Free lesson

Verify real HTML and crawlable links

Verify real HTML and crawlable links — SEO for an AI-built website. Inspect what is delivered; Inspect responses locally; Check missing routes honestly. Practical assignment: Lab evidence.

Demo edition. The materials are undergoing editorial review.

Topics covered

  • Inspect what is delivered
  • Inspect responses locally
  • Check missing routes honestly

Inspect what is delivered

View source and inspect rendered content. Important workshop facts and real links should exist in the site output; a screenshot or canvas-only page is insufficient evidence.

The example site offers fictional workshop information in four languages. Treat every search phrase as a hypothesis about a reader’s task, not measured demand. AI may organize a brief or suggest titles, but it cannot supply invented search volume, reviews, addresses or guarantees. Keep an audit table with URL, observed response, content purpose and proposed change. Separate a local implementation check from evidence collected on a published domain.

Inspect responses locally

Run the site’s local server and fetch its actual route. Replace the sample port with yours. Save status and HTML so missing content can be reproduced.

Compare an existing route with a deliberately missing route. If both return 200 with identical content, investigate the host’s fallback configuration. A client-side not-found message alone may still be delivered as a successful HTTP response, which is a different technical condition from a genuine 404.

Apply metadata to the actual HTML head or the framework’s supported metadata API, not just an assistant’s text description. Replace the reserved workshop.example domain only when you own and publish a real domain; it cannot be submitted as your property. Inspect raw response and rendered page separately. A correct-looking browser tab does not prove canonical links, language alternatives or structured data are present in the delivered document.

curl -i http://127.0.0.1:3000/en/workshop/
# Inspect: HTTP status, title, headings, facts and href targets.
# A local response verifies implementation only; it is not Google indexing proof.

Check missing routes honestly

A nonexistent workshop should return not found rather than an empty success page. Redirect only when a real replacement exists; sending every missing URL home hides the problem.

Record what the implementation can prove and what depends on search-engine processing. A successful live fetch, sitemap submission, indexed URL and improved search traffic are different observations. Compare dates and use the same URLs when reviewing changes. Avoid repeating a request merely because results are not immediate. Search Console can reveal issues, but it does not turn an SEO checklist into a guarantee of ranking or revenue.

Practical assignment

Lab evidence

Continue to learning

Course outline

  1. Map search intent to useful pages
  2. Verify real HTML and crawlable links
  3. Set titles, descriptions and canonicals
  4. Connect four language versions
  5. Build a truthful sitemap and structured data
  6. Use Search Console as evidence