Are URLs with # really invisible for Google SEO?

What exactly is a fragment identifier and how does it work?

A fragment identifier is the part of a URL that appears after the hash symbol (#). Technically, it does not trigger a new HTTP request on the server side. The browser loads the entire page and then automatically scrolls to the corresponding HTML element with the matching ID.

This mechanism is purely client-side. The server only receives the portion before the #, which is why traditional search engines have always treated these variations as duplicates of the same resource. Mueller's statement confirms that Google maintains this approach for indexing.

Why doesn't Google differentiate these URLs for ranking?

The HTML content remains the same regardless of the anchor used. Google indexes the complete document, not its fragments. Differentiating these URLs would create massive confusion in the index and artificially increase duplicates without added value.

This logic also protects against easy manipulation: a site cannot artificially create dozens of unique “pages” just by adding different anchors. The consistency of the index takes precedence over extreme granularity.

How does Google utilize these identifiers for snippets then?

Even though Google ignores fragments for indexing, it can use them for display purposes. When a result points to a specific relevant section for the query, Google may display a rich snippet including the # in the clickable URL.

This feature enhances user experience by directing users straight to the relevant paragraph, without altering PageRank, crawl budget, or ranking signals. It's a cosmetic optimization post-indexation, not a ranking factor.

• URLs with # all point to the same indexed resource — no duplication in Google’s index
• No ranking impact: ranking signals remain unchanged regardless of whether an anchor is present
• No influence on featured snippets: their selection is based on the overall content of the page, not on fragments
• Possible cosmetic usage: Google can display snippets pointing to #section for better UX in SERPs
• No fragmentation of link equity: a backlink to page#A and one to page#B consolidate their juice on the same unique URL

Is this statement consistent with real-world observations?

Yes, largely. Empirical tests confirm that variations of anchors do not create distinct pages in the index. Search Console groups these URLs under a single canonical version, and backlink analysis tools aggregate the link equity without differentiating the fragments.

However, a nuance deserves to be highlighted: in some very specific cases involving modern JavaScript frameworks (React Router, Vue Router in hash mode), we observe marginal behaviors where Google may temporarily crawl different “views” as distinct states. [To be confirmed] — this seems more related to JS architecture than to intentional differentiation of fragments by Google.

What confusions should be avoided at all costs?

Do not confuse fragment identifiers (#) and URL parameters (?param=value). The latter generate actual distinct server requests and can create unique pages in Google's eyes, with all the duplication risks that entails.

Another common pitfall: believing that anchors allow you to optimize multiple keywords on a single page by creating “SEO subpages”. This strategy is ineffective since Google indexes the overall content, not isolated sections. The thematic optimization should occur at the document level.

In what contexts might this rule seem contradicted?

Accelerated Mobile Pages (AMP) sometimes use fragment identifiers for advanced features, but their treatment remains consistent: Google indexes the complete AMP page. Featured snippets occasionally display deep links with #, but this is a visual enhancement post-indexation.

More problematic: some Single Page Application (SPA) sites use hash routing to avoid server configuration. Google can crawl these states if the JavaScript executes correctly, but it is the DOM manipulation by JS that creates content variations, not the fragment identifier itself. Let's be honest — this architecture remains suboptimal for SEO.

What should you concretely do with fragment identifiers?

Use them solely for their primary function: to improve internal navigation and the user experience. A summary at the top of a long article pointing to #section1, #section2 helps your readers without disrupting your SEO. This is their legitimate use.

Do not try to create artificial SEO variations by multiplying anchors. Each internal link to page#variant dilutes your crawl consistency without providing any indexing benefit. Prioritize clean and hierarchical URLs if you really need to segment content.

How can you check that your structure isn’t penalized by poor usage?

Check the Search Console: if you see dozens of variations of the same URL with different fragments in the coverage report, that’s a bad sign. It likely indicates that your internal linking or backlinks anarchically point to different anchors.

Analyze your server logs: Googlebot should only request URLs without fragments. If you detect suspicious crawls with #, it suggests your JS architecture is generating abnormal requests or that server-side redirections are mishandling these URLs. And that's where the problem lies.

What mistakes should you absolutely avoid in your site's architecture?

Never point strategic backlinks to URLs with fragments. Always request the clean version of the URL to maximize link equity consolidation. A quality link to page#section loses its targeted precision without gaining SEO strength.

Avoid canonicals or hreflang including fragments. Google ignores them in these tags, which can create inconsistencies in your technical marking. Stick to clean URLs for all your structural signals.

• Audit your internal linking to remove unnecessary links to variations with #
• Ensure that your quality backlinks point to clean URLs without fragments
• Check that your XML sitemap does not contain any URL with a fragment identifier
• Make sure your canonical, hreflang, and og:url tags always use the version without #
• Test that Googlebot can access your content if you use JavaScript routing, regardless of the fragments
• Clearly document for your writers and developers that anchors are UX tools, not SEO