SEO Audit

Audit date: 2026-07-15

Scope

This audit covers the live GitHub Pages site, the HonKit source, the shared templates, built HTML output, existing validation scripts, and the GitHub repository presentation.

Baseline Findings

Crawlability and Indexing

Severity Finding Evidence Affected surface
Critical No robots.txt on the live site https://ankitparekh007.github.io/ai-tools-cheatsheets/robots.txt returned 404 during audit live site
Critical No XML sitemap on the live site https://ankitparekh007.github.io/ai-tools-cheatsheets/sitemap.xml returned 404 during audit live site
High No canonical tags on built pages _book/index.html and _book/tools/claude-code.html contained no canonical tag shared output
High Duplicate public routes exist for some pages both /tools/claude-code and /tools/claude-code.html returned 200 GitHub Pages route handling
Medium SEO strategy docs and landing pages did not exist no docs/seo/ directory; no audience-path pages in navigation source docs

Search Presentation

Severity Finding Evidence Affected surface
Critical No Open Graph metadata live homepage source contained no og: tags live site
Critical No Twitter/X metadata live homepage source contained no twitter: tags live site
Critical No structured data live homepage source contained no application/ld+json live site
High Meta descriptions were effectively empty on content pages _book/tools/claude-code.html rendered <meta name="description" content=""> built output
High Titles were generic rather than intent-optimized built titles followed Page - AI Tools Cheatsheets defaults built output
Medium No audience landing pages for developers, teams, or leaders current navigation had no audience-specific paths source docs

Content and Intent

Severity Finding Evidence Affected surface
High No metadata inventory or topic map existed no metadata inventory or SEO content strategy docs were present repo docs
Medium Homepage did not route different audiences cleanly current homepage linked sections but not audience-based entry points docs homepage
Medium Internal linking was strong within sections but weak across audience journeys no curated paths for teams, leaders, or platform/security docs navigation
Opportunity Existing tool, workflow, MCP, and governance content is deep enough to support stronger search intent targeting current section pages and audits show substantial technical content content strategy

Performance and Experience

Severity Finding Evidence Affected surface
Medium No Lighthouse or Core Web Vitals baseline was documented no existing SEO/performance audit docs repo docs
Medium Site assets are custom but not SEO-audited custom CSS, JS, and search UX exist without measurement docs docs assets
Opportunity HonKit output is static and lightweight enough for good crawlability if metadata is added correctly no server-side app complexity or API rendering site architecture

GitHub Discoverability

Severity Finding Evidence Affected surface
Medium Repository description was good but not fully aligned to organization intent current description emphasized cheat sheets more than governance/adoption value GitHub repo
Low Topics were strong but missing a few adoption-oriented terms current topics included AI tools and MCP but not every growth target GitHub repo
Opportunity A public v1.0.0 release already exists repository now has a shareable launch milestone GitHub releases

Current Strengths

  • stable public URLs and navigation
  • strong technical depth in tools, workflows, MCP, templates, and governance
  • explicit verification philosophy and security-first positioning
  • working documentation validation and GitHub Pages deployment pipeline
  • readable favicon set and polished docs UI

Implementation Priorities

  1. Add a page metadata system with unique titles and descriptions.
  2. Add canonical tags to resolve duplicate .html and extensionless routes.
  3. Generate sitemap.xml, robots.txt, and optional llms.txt.
  4. Add Open Graph, Twitter, and JSON-LD structured data.
  5. Create audience landing pages and an intent/topic map.
  6. Add SEO validation automation to the docs pipeline.

Audit Status

This audit describes the confirmed pre-implementation baseline. Follow-up files in docs/seo/ define the implementation and measurement plan.