Practical Lens 31: index.html can create a second “homepage”

If both / and /index.html are crawlable, AI crawlers may treat them as separate homepage variants and weaken the primary identity signal.

What this lens means

If the root homepage and /index.html both return valid content, crawlers can discover two URLs for the same primary surface. That makes the homepage less canonical and can split identity signals across two variants.

Why this happens

  • The root URL appears in navigation, external links, profiles and sitemaps.
  • The /index.html URL can still be found through old internal links, server defaults, legacy CMS output or copied references.
  • If redirects and canonicals do not enforce the root URL, both variants can remain plausible homepage candidates.

What this usually indicates

  • Homepage alternation: AI cites / in one place and /index.html in another.
  • Duplicate discovery: both URLs return similar homepage content.
  • Mixed internal links: some links point to / while others point to /index.html.
  • Canonical weakness: the canonical URL does not clearly enforce the root homepage.

What to verify (evidence-only)

  • Does /index.html redirect to / with one final canonical URL?
  • Does the canonical tag on the homepage point to https://verisai.eu/ or the preferred root URL?
  • Does the sitemap list only the root homepage, not /index.html?
  • Do internal links use only the preferred homepage URL?
  • Do crawler user agents and normal requests resolve to the same final URL?

Terminal check example

Replace example.com with the audited domain. The goal is to confirm final URL resolution and canonical consistency.

curl -I https://example.com/
curl -I https://example.com/index.html
curl -L -s -o /dev/null -w '%{url_effective}\n' https://example.com/index.html

PowerShell check example

Use this on Windows environments to inspect the resolved URL and canonical behavior.

(Invoke-WebRequest -Uri 'https://example.com/' -MaximumRedirection 0 -ErrorAction SilentlyContinue).Headers.Location
(Invoke-WebRequest -Uri 'https://example.com/index.html' -MaximumRedirection 5).BaseResponse.ResponseUri.AbsoluteUri

Frequently Asked Questions

Why does /index.html matter for AI crawlers?

Because / and /index.html can look like two separate homepage URLs if the server does not normalize them.

Which homepage variant should be canonical?

Usually the root URL is preferred. The important point is to choose one final URL and enforce it consistently.

What is the fastest check?

Request / and /index.html and confirm that both resolve to one final homepage URL with one matching canonical tag.

← Back to Practical Lens library