Hreflang Has No Return Tag and Google Ignores the Cluster
Search Console reports "No return tags" on your hreflang cluster. Page A points to page B, but B doesn't point back to A. Google ignores the whole annotation.
URL unknown, Crawled / Discovered not indexed, sitemap submitted but not indexed, orphan pages, category / tag pages, new-site delays.
Google indexing is complex, but 80% of cases land on a handful of Search Console states: URL is unknown, Crawled — currently not indexed, Discovered — currently not indexed, Duplicate. One article per state — what the field means, when waiting is normal vs. when your structure is broken, and the shortest path to fix. We also separate the three most-misunderstood truths: submitting a sitemap does not guarantee indexing, URL Inspection does not force indexing, and slow indexing is not always a technical error.
Search Console reports "No return tags" on your hreflang cluster. Page A points to page B, but B doesn't point back to A. Google ignores the whole annotation.
Your SPA renders fine for users, but Search Console shows the page indexed with a blank `<body>`. Why Googlebot's rendering quirks lose your content — and how to fix it.
You got the Search Console email confirming mobile-first indexing. Two weeks later, pages and impressions drop. The desktop version had content the mobile version doesn't.
A common SEO myth says set `noindex,follow` on page 2+. Google treats long-term noindex,follow as noindex,nofollow — and your deep articles stop getting discovered.
Search Console reports thousands of duplicate URLs with `?utm_*`, `?sort=`, `?ref=` variants. Each parameter combination got indexed as a separate page.
You disallowed `/assets/` or `/_next/static/` in robots.txt to "save crawl budget." Googlebot can no longer render your page. Rankings and rich results decline.
Your sitemap.xml has 73,000 URLs in a single file. Search Console reports "Couldn't fetch" or processes only the first 50,000. How to split a sitemap correctly.
A previously well-ranking page disappears from Google. Sometimes this is a quality update, sometimes a manual action. How to tell which.
Crawl Stats show Googlebot fetching hundreds of URLs per day, but the Performance report stays at the same flat impression line. Why crawling does not equal traffic.
After redesigning the site, the indexed page count drops in Search Console. What is real damage vs. normal re-evaluation.
A new domain has been live for 4–8 weeks. Sitemap is submitted, URL Inspection shows pages as "Discovered". Nothing seems to be moving forward.
The "Indexed" line in Search Console drops by 50–200 URLs overnight. No errors, no changes. What is going on.
Google quietly stops crawling and indexing the thinnest pages on a site, even if there is no explicit penalty.
The Removals tool in Search Console blocks a URL from appearing in search for ~6 months. People misuse it as a permanent delete or a "fix indexing" button.
Search Console says alternate — it's not an error. Here's how to read it.
Wrong canonical leads to dropped pages or wrong URL ranking.
Description in SERP isn't yours — usually too generic, missing the keyword, or duplicated across pages.
You set a canonical but Google picked another URL. Why and how to fix.
What hreflang warnings mean, why mismatched clusters happen, and the minimal fixes that resolve return-tag and language-code errors. For the Search Console International Targeting workflow, see the linked page.
Brand-new domain takes weeks to start ranking. Here's what actually helps.
Short, thin pages get deprioritized. What "depth" really means.
Search Console flagged pages as not mobile-friendly. Typically viewport, tap targets, or content cut-off.
Indexed status, zero impressions. Usually content depth, intent mismatch, or topical authority.
The 7 most common "not indexed" reasons and the right fix for each.
Google flagged your page as "Soft 404" — content too thin to be a real page.
JSON-LD warnings — typically missing required fields, wrong type, or out-of-spec fields.
Google replaces your title with H1 / sitename. Usually title quality, keyword stuffing, or relevance.
noindex blocks indexing. robots.txt blocks crawling. They are not the same. A short table for when to use which, and the most common mistake that breaks both.