Old AJAX Crawling Scheme Meta Fragment Tag
What This Means
The page contains <meta name="fragment" content="!"> in its <head>. This tag was part of Google's AJAX Crawling Specification — a protocol designed in 2009 to make JavaScript-rendered content crawlable by instructing Googlebot to fetch a separate "escaped fragment" URL instead of the JavaScript-rendered version.
Why It Matters for SEO
Google officially deprecated the AJAX crawling scheme in 2015 and ended support entirely in 2018. Googlebot now renders JavaScript directly and no longer needs or uses this protocol. A page with the meta fragment tag is giving Googlebot an instruction it no longer follows — but it may still trigger: the generation of ?_escaped_fragment_= URL variants that can appear as separate (potentially duplicate) pages in the crawl, confusion in older or third-party crawlers that do attempt to honor the directive, and a signal of technically outdated page infrastructure.
This is a warning because the risk is real — the escaped fragment URL variants can create genuine crawl and indexation issues — but the tag itself is benign in isolation on most modern sites.
What the Platform Checks
The platform scans the page <head> for <meta name="fragment" content="!">. Fires on presence of the tag.
How to Fix It
Remove the meta fragment tag entirely. It serves no purpose on modern web infrastructure:
- In CMS templates: search for "meta name=\"fragment\"" in all theme and plugin files and remove the tag.
- In custom code: remove the tag from the base HTML template.
- If your application used hashbang URLs (
#!): also migrate away from hashbang URL patterns. Replace them with standard URLs using HTML5 History API (pushState) routing and ensure content is server-rendered or pre-rendered without requiring the AJAX crawling protocol.
After removing, check Google Search Console's Coverage report to see if any ?_escaped_fragment_= URLs were indexed, and if so, 404 them or redirect them to the canonical URL.
Find every pagewith deprecated AJAX tags
The audit identifies every page still using the old AJAX crawling directive so you can remove it from templates.