GA4 Error Pages: find 404 pages by their title

The Error Pages report finds the pages your visitors saw as errors by matching the page titles GA4 recorded against filters you save, such as titles containing "404" or "Page not found". It shows which paths produced them, how many sessions and views they had, and what share of all sessions ran into one, so broken links and removed pages surface from real visits rather than from a crawl.

Why it matches page titles

GA4 records the path and the title of every page view (pageTitle, "the web page titles used on your site", in the Data API schema). A site's error template usually has a title of its own, so the title is a dependable marker that needs no extra tagging. The report asks GA4 for page paths with their titles and keeps the ones whose title matches a filter.

Setting up the title filters

The report fetches nothing until at least one filter exists.

1. Pick a match type: contains, exactly matches, starts with, ends with or matches regex.
2. Type the title text, for example 404, and click Save filter. Or click a suggestion: contains "404", "Page not found", "Server error" or "Error".
3. Add as many as you need, up to 20. A page counts when its title matches any one of them.

Matching ignores case. A regex filter matches anywhere in the title unless you anchor it with ^ and $. Be careful with broad terms: contains "Error" also catches a guide titled "Error handling in forms", so check the table after adding it and replace it with something narrower if it does.

Filters are saved for the property, and the LLM Traffic report reuses them for its own error table. Only the property's owner can change them. The demo property keeps the suggested filters.

What the report shows

• Five cards: Error Sessions, Error Views, Active Users, Bounce Rate, and Share of All Sessions, which divides error sessions by every session in the segment. On the first four, a rise is shown as bad news.
• A bar chart of the ten matching pages with the most sessions.
• A table with Page Title, Page, Sessions, Views, Active Users and Bounce Rate, searchable by path or title, 50 rows to a page.

If GA4 returns several titles for one path, the numbers are added together under the first title.

Fixing what you find

Work down the table from the most sessions:

1. Decide what each path should be. Restore the page, redirect it to the closest live page, or leave it as a 404 when nothing replaces it.
2. Find what links to it. Search your own templates and content for links to the path and correct them. Links on other sites and old bookmarks are out of your hands, which is what a redirect is for.
3. Check the status code. An error page that answers with a 200 status is what Google calls a soft 404 (soft 404 errors). Run the path through URL Inspection to see what Google received.
4. Watch Share of All Sessions after the fixes. It should fall over the following weeks.

The report can only see error pages that carry your GA4 tag. If your error template does not load the tag, its visits never reach GA4 and nothing appears here. For the errors Google found while crawling, see 404 errors in Search Console.