SEO & Bing compliance: fix title duplication, canonical URLs, IndexNow, heading hierarchy, and internal linking

[Copilot]

Addresses Bing Webmaster Guidelines compliance gaps and several concrete SEO bugs across all 5 pages.

Bug Fixes

• Title double-suffix — Root layout defines template: "%s | ReadmeGenAI". All child pages were setting plain string titles like "Documentation | ReadmeGenAI", causing Next.js to render "Documentation | ReadmeGenAI | ReadmeGenAI". Fixed by switching every page to title: { absolute: "..." }:

  // Before (broken)
  export const metadata: Metadata = { title: "Documentation | ReadmeGenAI" };
  // After
  export const metadata: Metadata = { title: { absolute: "Documentation | ReadmeGenAI" } };

• Broken OG image — Root layout referenced non-existent /og-image.png; replaced with existing /ReadmeGenAI.png and improved alt text.

• Footer GitHub link — href="#" replaced with https://github.com/BeyteFlow/ReadmeGenAI (target="_blank", rel="noopener noreferrer").

• Navbar logo not crawlable — Brand <div> wrapped in <Link href="/"> with aria-label, making the home link discoverable by crawlers and keyboard users.

SEO Enhancements

• Canonical URLs — Added alternates: { canonical: "/<path>" } to all 5 pages to eliminate duplicate-content signals.

• IndexNow API route — New POST /api/indexnow submits all 5 URLs to Bing's IndexNow API using the existing key file (/public/85f2c293fce3483d896a5d9dc98974e5.txt). Includes network error handling and uses server-only SITE_URL env var (falls back to NEXT_PUBLIC_SITE_URL then the hardcoded production URL).

• Heading hierarchy — Home page had five competing <h2> tags in SEOSection. Demoted "Key Benefits" and the four sub-feature headings to <h3>, leaving a single <h2> ("Why Use an AI README Generator?") per section.

• Sitemap lint warning — Removed unused config parameter from next-sitemap.config.js.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• fonts.googleapis.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node node /home/REDACTED/work/ReadmeGenAI/ReadmeGenAI/node_modules/.bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
readme-gen-ai	Ready	Preview, Comment	Mar 6, 2026 8:32am