Implement SEO and GEO best practices

Create XML sitemap at /sitemap.xml listing all public routes. Include lastmod dates and priorities: homepage 1.0, main pages 0.8, blog posts 0.6.

• Publish your project so the sitemap file is live
• Check that it is accessible at: https://yourdomain.com/sitemap.xml (should return XML)
• Check all key routes included (home, main pages, blog, products)
• Update lastmod whenever content changes
• Use priority to indicate importance (0.0–1.0)
• Submit to Google Search Console and Bing Webmaster Tools
• Regenerate and resubmit when adding/removing pages (not automatic). For example, prompt:

  Update sitemap.xml to include /new-page and remove /old-page then resubmit to Google Search Console.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://yourdomain.com/</loc>
    <lastmod>2025-01-15</lastmod>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://yourdomain.com/about</loc>
    <lastmod>2025-01-15</lastmod>
    <priority>0.8</priority>
  </url>
</urlset>

Create robots.txt at /public/robots.txt that allows all crawlers, references Sitemap: https://yourdomain.com/sitemap.xml, and allows GPTBot and PerplexityBot for AI visibility.

• Check that it is accessible at: https://yourdomain.com/robots.txt
• Never block CSS, JavaScript, or /assets/ folder
• Includes Sitemap: line pointing to your sitemap
• Controls AI bot access (GPTBot, PerplexityBot) based on your strategy

User-agent: *
Allow: /
Sitemap: https://yourdomain.com/sitemap.xml

User-agent: GPTBot
Allow: /

Add canonical tags to all pages pointing to their own URLs. Use https://yourdomain.com format with no trailing slash.

• Check each page. Paste this in the browser console:
  Copy

  Ask AI

  console.log('Canonical:', document.querySelector('link[rel="canonical"]')?.href);
  

• Confirm exactly one canonical tag exists per page.
• Make sure it matches your preferred domain and URL variant (HTTPS, trailing slash).
• Avoid pointing different pages to the same canonical unless it’s intentional (for example, filtered product views).

Review all routes and make sure URLs are clean and descriptive. Use hyphens for word separation and avoid query parameters.

• Navigate to each route and check browser console for errors
• URLs should be: stable, descriptive, no random IDs
• Consistent format site-wide (trailing slash or not, www or not)
• All routes load without JavaScript errors

Add 3-5 contextual internal links to related pages. Use descriptive anchor text instead of ‘click here’.

• Check that links are crawlable. The number should roughly match what you expect based on your navigation and content.
  Copy

  Ask AI

  console.log('Links:', document.querySelectorAll('a[href]').length);
  

• Use real <a href> tags, not onClick handlers
• Important pages have multiple internal links pointing to them
• Include links to your most important pages in the footer so they appear site-wide
• Anchor text is descriptive with keywords (not “click here”)
  • Good anchor text: organic dog food benefits
  • Bad anchor text: click here, read more
• Deep pages reachable within 3 clicks from homepage

Update the page titles for all routes. Use clear, descriptive titles that match each page’s purpose, and keep them under 60 characters.

• Check title content and length for each page. Paste this in the browser console:
  Copy

  Ask AI

  console.log('Title:', document.title, '| Length:', document.title.length);
  

• Each route has unique, descriptive title (not generic Home everywhere)
• Under 60 characters to avoid truncation
• Includes primary keyword plus brand name

Write unique meta descriptions for all key pages. Keep each one clear, helpful, and between 140–160 characters.

• Check description and length for each page. Paste this in the browser console:
  Copy

  Ask AI

  console.log('Desc:', document.querySelector('meta[name="description"]')?.content, '| Length:', document.querySelector('meta[name="description"]')?.content.length);
  

• Each page has unique description (140-160 characters)
  • Bad: Welcome to our website (generic, repeated)
  • Good: Premium organic dog food delivered fresh to your door. Free shipping over $50. (158 chars)
• Highlights benefits, differentiation, and a soft call to action
• Not duplicated across pages

Review the heading structure on each page. There should be one H1 at the top, with H2 for major sections and H3 for nested content. Don’t skip heading levels.

• Check there is only one H1 tag. Paste this in the browser console - should return 1:
  Copy

  Ask AI

  console.log('H1s:', document.querySelectorAll('h1').length);
  

• View heading content. Paste this in the browser console:
  Copy

  Ask AI

  console.log('H1:', document.querySelector('h1')?.textContent);
  

• H1 includes primary keyword and states page purpose
• Headings flow logically (H1 → H2 → H3, never skip levels)
• Headings are not used purely for styling

Review the HTML structure and use semantic tags where appropriate. Place main content in <main>, navigation in <nav>, sections in <section>, and footer content in <footer>.

• Paste this in the browser console - should return true as applicable:

console.log('Has <main>:', !!document.querySelector('main'));
console.log('Has <nav>:', !!document.querySelector('nav'));
console.log('Has <footer>:', !!document.querySelector('footer'));
console.log('Has <section>:', !!document.querySelector('section'));

• Check the following for each page:
  • Single <main> wraps primary content
  • Navigation inside <nav>
  • Footer content in <footer>
  • Related content in <section> and <article> tags

Review all images and add clear, descriptive alt text. Make sure each image has width and height attributes and is properly compressed for fast loading.

• Confirm every image has alt text. Paste this in browser console - should return 0:
  Copy

  Ask AI

  console.log('Missing alt:', document.querySelectorAll('img:not([alt])').length);
  

• Evaluate alt text quality - must be descriptive with relevant keywords
  • Bad: alt="image" , alt="photo", alt=""
  • Good: alt="Golden retriever eating organic grain-free dog food from a bowl"
• Use proper file formats and keep file sizes small:
  • WebP for photos and illustrations
  • SVG for logos, icons, and simple graphics
  • Images compressed under 200KB
• Width/height attributes present (prevents layout shift)

1. Create link-worthy content

• In-depth guides, tutorials, and research
• Data, statistics, or original insights
• Interactive tools, calculators, ROI estimators
• Templates, checklists, and downloadable assets

2. Publish guest posts

• Contribute articles to blogs in your niche
• Include thoughtful contextual links to your site
• Use author bios to reinforce brand credibility

3. Partner with complementary businesses

• Co-produce content (articles, webinars, resources)
• Cross-link between relevant pages

4. Get listed in directories and resource pages

• Industry directories
• Local business listings
• Startup listings
• Curated resources relevant to your product

5. Promote content

• Share on social platforms
• Add to newsletters
• Encourage influencers, bloggers, or customers to reference it
• Use PR outreach for big updates or launches

• Relevant (same topic or industry)
• Authoritative (trusted domains)
• Editorial (earned, not paid)
• Anchor-text descriptive (naturally including relevant keywords)
• Placed in context (inside real content, not random footers or sidebar links)
• Avoid spammy tactics (link farms, low-quality directories, or paid link schemes), which can hurt rankings.

Add Product schema to the product pages with name, description, price, availability, image, brand, and rating details.

• Check presence on key pages (for example, home, products, blog posts, FAQ). Paste this in the browser console - should return 1 unless you intentionally added multiple schema types:

console.log('Schema:', document.querySelectorAll('script[type="application/ld+json"]').length);

• Validate with Google Rich Results Test
• Fix any errors or missing required fields
• Keep schema data synchronized with visible page content

Add unique Open Graph and Twitter metadata to every important page. Set a custom title, description, URL, and social image for each route. Use one 1200×630 JPG image per page and update og:image and twitter:image accordingly.

• Before sharing any URL, verify how it appears:
  • Facebook Sharing Debugger
  • X (Twitter) Card Validator
  • LinkedIn Post Inspector
• Each important page has unique og:title, og:description, og:image, og:url in the HTML
• Tags include twitter:card and twitter:image
• Preview shows correct title, description, image
• Images are 1200×630px, and under 1MB
• Visually consistent with brand
• Avoid using single generic image for every page

<meta property="og:title" content="Organic Dog Food Delivery | PetFood Co" />
<meta property="og:description" content="Premium grain-free dog food delivered fresh to your door." />
<meta property="og:image" content="https://yourdomain.com/og-image.jpg" />
<meta property="og:url" content="https://yourdomain.com/products" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:image" content="https://yourdomain.com/og-image.jpg" />

Improve homepage performance by compressing images, adding width/height attributes, deferring non-essential scripts, and preloading key assets. Target a Performance score of 90+ in Lighthouse.

• Run Speed tool in Lovable (Google Lighthouse audit)
• Target scores:
  • Performance: 90+
  • Accessibility: 90+
  • Best Practices: 90+
  • SEO: 100
• Fix pages with poor performance scores
• In GSC, check and fix Core Web Vitals targets:

Review mobile experience. Increase tap target sizes to minimum 48x48px, add spacing between interactive elements, ensure text is minimum 16px, fix any horizontal scroll on small screens.

• Using Chrome DevTools and real devices, test key pages on several device sizes — test iPhone, Android, and tablet sizes.
• Confirm all primary flows work smoothly on mobile
• No horizontal scrolling on any page
• Text readable without zooming (minimum 16px font size)
• Buttons/links at least 48×48px, with spacing between, and easily tappable
• Forms work properly on touch devices (large inputs, clear labels)
• Navigation accessible (hamburger menu functional)
• Images and videos fit within screen width
• Confirm theviewporttag exists. Paste this in the browser console:
  Copy

  Ask AI

  document.querySelector('meta[name="viewport"]')?.outerHTML
  

  and you should see: 
  Copy

  Ask AI

  <meta name="viewport" content="width=device-width, initial-scale=1">
  

Check the homepage to ensure important information is in plain HTML with clear headings. Add Organization schema including name, description, URL, logo, and social links.

• Put key facts in static HTML (for example, what you do, who you serve, pricing)
• Use clear headings (H2, H3) to structure information
• Add comprehensive schema: Organization, Product, FAQPage, Article
• Write in clear, factual language that AI can parse and cite
• Keep facts consistent across your site, schema, and external profiles.

Update robots.txt to allow GPTBot, PerplexityBot, and Claude-Web, and block Google-Extended and CCBot. Keep all standard search engine crawlers allowed.

• Decide visibility strategy: allow AI citations or block AI training
• Explicitly allow or block bots based on strategy
  • Common bots: GPTBot (ChatGPT), PerplexityBot, Claude-Web, Google-Extended (training), CCBot
• Re-check after changes to ensure desired bots aren’t accidentally blocked

User-agent: *
Allow: /

User-agent: GPTBot
Allow: /

User-agent: Google-Extended
Disallow: /

Update the FAQ answers to be short, direct, and easy for AI to quote. Begin with the main answer, include concrete facts, and remove vague marketing wording.

• Write clear answers to common questions in FAQ/Q&A format
• Use definition patterns that are easy to quote: “X is [clear definition]”
• Avoid vague marketing copy
• Create lists and bullet points for easy parsing
• Include statistics with sources when possible

• Bad: Amazing transformative solutions
• Good: USDA-certified organic dog food delivered weekly. Plans start at $45/month with free shipping over $50.

Create an /llm page that clearly explains what the company does, what it offers, how it’s different, pricing basics, FAQs, and how to contact us. Add Organization and FAQPage schema and organize the page with simple H2/H3 headings.

• The page is created at a clear URL such as /llm or /about-ai.
• Content is structured with clear H2/H3 headings.
• The page includes key information: company summary, products/services, differentiators, pricing model, contact details, and FAQs.
• Organization and FAQPage schema are present so AI systems can extract structured facts.
• Content is factual, concise, and quotable (avoid marketing fluff).
• Information is kept up to date as offerings change.

• DNS TXT record (recommended): add the TXT record in your domain provider’s DNS settings
• Meta tag verification: prompt Lovable to add the meta tag

Add GSC verification meta tag: <meta name=‘google-site-verification’ content=‘YOUR_CODE’ /> to the <head>

• HTML file upload: upload Google’s verification file and ask Lovable to place it at the site root (usually /public)

1. In GSC, go to Sitemaps
2. Enter your sitemap URL:
   https://yourdomain.com/sitemap.xml
3. Click Submit

• Confirm Google sees real content (not a blank page)
• Diagnose CSR rendering issues
• Check if key resources (JavaScript/CSS) are blocked

1. Enter the URL in the URL Inspection bar
2. Click Test Live URL
3. Open View Tested Page to check:
   • Screenshot of what Googlebot sees
   • Rendered HTML
   • Console errors
   • Blocked resources
4. Click Request Indexing for new or updated pages (rate limited)

• Coverage/Page indexing:
  • Indexed vs. excluded pages
  • Crawl errors and reasons for exclusion
  • Indexation trend over time
• Performance (search results):
  • Impressions, clicks, CTR, average position
  • Top queries and pages
  • Pages gaining or losing visibility
• Core Web Vitals:
  • Real-world LCP, INP, CLS
  • Identify slow and problematic pages
  • Compare mobile vs. desktop performance
• Mobile usability:
  • Issues with tap targets, viewport, content width
  • Fix errors to maintain mobile rankings

• Check GSC Coverage for new errors and newly indexed pages
• Glance at search performance trends
• Run URL Inspection for newly important URLs and request indexing if needed

• Update sitemap.xml if pages changed
• Refresh underperforming titles and descriptions (low CTR pages)
• Run the built-in Speed tool (Lighthouse audit)
• Do a small round of content improvements or link building

• Do a deeper technical audit: canonicals, robots.txt, schema, internal links, mobile usability
• Review keyword performance and top landing pages
• Refresh older or declining content