Skip to content
Automation Club
  • MarkdownWhy Google skips the beans page, and the fixesExample output

    Why Google skips the beans page, and the fixes

    Ten fixes, most important first


    Verdict: the page tells Google to leave it out of search results. The line <meta name="robots" content="noindex, nofollow"> does that on its own, whatever else is on the page.

    I checked the page source you pasted against your three searches: "fresh roasted coffee beans", "buy coffee beans online" and "coffee beans Harbour Street". Here is what to fix, most important first.

    Fixes, most important first

    1. Delete the line that hides the page from Google

    Impact: High · Time: 2 minutes

    • What we found: the head of the page contains <meta name="robots" content="noindex, nofollow">.
    • Why it matters: "noindex" tells Google not to show this page in results at all, and "nofollow" tells it not to follow the page's links to your other pages, so nothing else on this list can help until the line is gone.
    • Fix: delete that whole line on the live site. Don't replace it with anything: with no robots line, Google treats the page as fine to list. If you edit the site through a site builder rather than the code, look for a setting called something like "hide from search engines" or "discourage search engines" and switch it off for the live site. Keep it switched on for any test copy of the site, so the test copy stays out of Google.

    2. Point the canonical link at your live page, not the test site

    Impact: High · Time: 5 minutes

    • What we found: <link rel="canonical" href="https://staging.northwind.example.com/shop"> names your staging address (a test copy of the site) as the real version of this page.

    • Why it matters: a canonical link tells Google which address is the main copy of a page, so this one points Google at the test site instead of the page your customers use.

    • Fix: change the address to this page's own live address, exactly as it shows in your browser bar. If that is https://northwind.example.com/shop, the line becomes:

      <link rel="canonical" href="https://northwind.example.com/shop">
      

      This line and the noindex line both look like leftovers from the test site, so check the source of your other pages for noindex and staging. as well.

    3. Give the page a title that says what it sells

    Impact: High · Time: 5 minutes

    • What we found: the title is <title>Shop | Home</title>, which doesn't mention coffee, beans or Northwind Coffee.

    • Why it matters: the title is usually the blue headline of your result in Google and one of the strongest clues to what the page is about, and "Shop | Home" matches none of your searches.

    • Fix: replace it with:

      <title>Buy Fresh Roasted Coffee Beans Online | Northwind Coffee</title>
      

      That's 56 characters, short enough to show in full in most results, and it contains both "fresh roasted coffee beans" and "coffee beans online". If local customers matter more to you than online orders, use Fresh Roasted Coffee Beans in [your town] | Northwind Coffee instead, keeping the whole title to about 60 characters.

    4. Add one main heading (H1) that says "coffee beans"

    Impact: High · Time: 10 minutes

    • What we found: there is no H1 (the page's main headline in the code); the first heading is <h3>Our beans</h3> and the coffees are <h4> headings with nothing above them.

    • Why it matters: Google and screen readers use the main heading to understand what a page is about, and "Our beans" on a third level heading never says coffee.

    • Fix: change <h3>Our beans</h3> to:

      <h1>Fresh roasted coffee beans</h1>
      

      Then change each coffee's <h4> to <h2>, for example <h2>House Filter</h2>. Your theme may size the new headings differently; if they look wrong, adjust them in /assets/theme.css.

    5. Add words about the coffee

    Impact: High · Time: about an hour

    • What we found: the whole page has about 60 visible words, mostly menu labels, prices and "Add to cart", and the word "coffee" appears once, in © 2026 Northwind Coffee.

    • Why it matters: Google matches pages to searches mostly through the words on them, so a page that never describes its coffee in a sentence has very little to match "fresh roasted coffee beans" or "buy coffee beans online".

    • Fix: put a short intro under the new H1. This one uses only what your page already says:

      <p>Northwind Coffee roasts its coffee beans fresh every Tuesday. Buy them online in 250g bags with delivery for $5, free on orders over $40. Or visit our cafes on Harbour Street and at the Old Mill.</p>
      

      Then add two or three sentences under each coffee. Fill in the brackets with what you'd tell a customer at the counter, and write only what's true:

      <h2>House Filter</h2>
      <p>[What it tastes like]. [Light, medium or dark roast], from [where the beans come from]. Good for [filter, plunger or espresso]. [Sold as whole beans or ground.]</p>
      

      For the Single Origin of the Month, one line explaining the monthly pick and naming this month's coffee works well.

    6. Put the beans page in the main menu

    Impact: Medium · Time: 5 minutes

    • What we found: the menu has Home, Our cafes, Videos and Contact, but no link to the shop (/shop, going by the canonical line).

    • Why it matters: Google finds pages and judges how important they are largely by the links pointing to them, and a menu link usually appears on every page of the site.

    • Fix: add this inside <nav>, after the Home link:

      <a href="/shop">Coffee beans</a>
      

      Use the page's real path if it isn't /shop. I can only see this page's menu, so if your home page already links to the shop in another way, this still helps but matters a little less.

    7. Add a meta description

    Impact: Medium · Time: 5 minutes

    • What we found: there is no <meta name="description"> line in the head.

    • Why it matters: the description is often the two lines of text under your title in Google, and without one Google picks text from the page, which here could be "Add to cart" or "Click here for more info".

    • Fix: paste this under the title line:

      <meta name="description" content="Fresh coffee beans roasted every Tuesday. Buy online from $15 a 250g bag, free delivery over $40, or visit our cafes on Harbour Street and at the Old Mill.">
      

      It's 155 characters and uses only facts from your page. Google sometimes rewrites descriptions, but it often uses a good one. Update it if your prices or delivery charge change.

    8. Write out your cafe addresses, hours and phone number

    Impact: Medium · Time: 20 minutes

    • What we found: the only location text is Visit us! Harbour Street and the Old Mill., with no street numbers, town, opening hours or phone number.

    • Why it matters: for searches like "coffee beans Harbour Street", Google looks for a full address it can match to your Google Business Profile (your listing on Google Maps), and a street name alone gives it little to go on.

    • Fix: replace that footer line with your details, written exactly as they appear on your Google Business Profile:

      <p>Visit our cafes:<br>
      Harbour Street: [number] Harbour Street, [town] [postcode]. Open [days and hours]. Phone [number].<br>
      The Old Mill: [street address], [town] [postcode]. Open [days and hours]. Phone [number].<br>
      <a href="/cafes">More about our cafes</a></p>
      

      If the footer is shared across your site, this one change helps every page. If either cafe doesn't have a Google Business Profile yet, setting one up is free and is the main way to appear on Google Maps.

    9. Describe your photos with alt text

    Impact: Low · Time: 15 minutes

    • What we found: none of the six images has alt text (a short written description of an image, kept in the code), for example <img src="/images/IMG_2077.jpg"> for the House Filter, and the logo link <a href="/"><img src="/images/logo-final-v3.png" width="180"></a> has no words at all.

    • Why it matters: Google relies mostly on alt text to know what a photo shows, so without it your product photos are unlikely to appear in Google Images, and people using screen readers hear nothing for them.

    • Fix: add an alt to each image:

      <img src="/images/logo-final-v3.png" width="180" alt="Northwind Coffee home">
      <img src="/images/IMG_2041.jpg" alt="[what the photo shows, in a few words]">
      <img src="/images/IMG_2077.jpg" alt="House Filter coffee beans">
      <img src="/images/IMG_2081.jpg" alt="Single Origin of the Month coffee beans">
      <img src="/images/IMG_2090.jpg" alt="Espresso Blend coffee beans">
      <img src="/images/IMG_2093.jpg" alt="Decaf coffee beans">
      

      While you're there, renaming the files (for example IMG_2077.jpg to house-filter-coffee-beans.jpg) helps a little more. Update each src to match.

    10. Add product details Google can read directly (structured data)

    Impact: Low · Time: 30 minutes

    • What we found: there is no <script type="application/ld+json"> block on the page.

    • Why it matters: structured data is a hidden block of code that lists your products and prices in a format Google reads directly; it's optional, but it makes it possible for your results to show prices.

    • Fix: paste this just before </head>. Replace [currency] with your three letter currency code (for example USD, AUD or NZD), and northwind.example.com with your live address if it's different:

      <script type="application/ld+json">
      {
        "@context": "https://schema.org",
        "@graph": [
          {
            "@type": "Product",
            "name": "House Filter",
            "description": "250g bag of coffee beans, roasted every Tuesday.",
            "image": "https://northwind.example.com/images/IMG_2077.jpg",
            "brand": { "@type": "Brand", "name": "Northwind Coffee" },
            "offers": { "@type": "Offer", "price": "16.00", "priceCurrency": "[currency]" }
          },
          {
            "@type": "Product",
            "name": "Single Origin of the Month",
            "description": "250g bag of coffee beans, roasted every Tuesday.",
            "image": "https://northwind.example.com/images/IMG_2081.jpg",
            "brand": { "@type": "Brand", "name": "Northwind Coffee" },
            "offers": { "@type": "Offer", "price": "19.00", "priceCurrency": "[currency]" }
          },
          {
            "@type": "Product",
            "name": "Espresso Blend",
            "description": "250g bag of coffee beans, roasted every Tuesday.",
            "image": "https://northwind.example.com/images/IMG_2090.jpg",
            "brand": { "@type": "Brand", "name": "Northwind Coffee" },
            "offers": { "@type": "Offer", "price": "15.00", "priceCurrency": "[currency]" }
          },
          {
            "@type": "Product",
            "name": "Decaf",
            "description": "250g bag of coffee beans, roasted every Tuesday.",
            "image": "https://northwind.example.com/images/IMG_2093.jpg",
            "brand": { "@type": "Brand", "name": "Northwind Coffee" },
            "offers": { "@type": "Offer", "price": "17.00", "priceCurrency": "[currency]" }
          }
        ]
      }
      </script>
      

      If you renamed the photos in fix 9, use the new names here. Then paste your page address into Google's free Rich Results Test (search.google.com/test/rich-results) to check Google reads it correctly. Keep the prices here in step with the page when they change.

    Also failed, smaller: the delivery link just says "here" (Click <a href="/delivery">here</a> for more info.), so change it to See our <a href="/delivery">delivery details</a>.; and the page doesn't say what language it's in, so change <html> to <html lang="en">.

    What I could not check

    The page source can't show these. Google Search Console is free: you prove you own the site once, then:

    • Whether Google has the page at all, and what it last saw. Paste the live page address into the URL Inspection box at the top of Search Console. Once fixes 1 and 2 are live, click "Request indexing". Google still has to visit and process the page again, which can take from a few days to a few weeks.
    • Your robots.txt file, a separate file that can block pages across the whole site. Open https://[your live address]/robots.txt in a browser and look for Disallow: / or Disallow: /shop. The robots.txt report in Search Console (under Settings) shows the version Google fetched.
    • How fast the page loads for real visitors. File names like IMG_2077.jpg often mean photos straight off a phone or camera, which can be several megabytes each and slow on mobile data. The Core Web Vitals report in Search Console shows real visitor speed once the site has enough traffic; until then, PageSpeed Insights (pagespeed.web.dev) tests the page for free.
    • Who links to the page. The Links report in Search Console shows which other sites, and which of your own pages, link to it.
    • Whether your staging site is in Google. Search Google for site:staging.northwind.example.com. If anything shows up, put the staging site behind a password so it can't compete with your live site.
    • How it looks on a phone. The viewport line is right, but the styles live in theme.css, which wasn't in what you pasted. Open the page on your phone and check that the text is easy to read and the Add to cart buttons are easy to tap.

    Go deeper: for tracking where you rank over time and checking your whole site at once, OpenSEO (github.com/every-app/open-seo) is an open-source tool you can host yourself or rent. It's a separate tool, not part of this check.

    Made with Claude Code · Skill

    Markdown · Document

    The fix list. A real run on the pasted source of a made-up coffee shop page, with web fetch off. The page and its problems are made up.

Works with

  • Claude
  • Claude Code
  • ChatGPT
  • +18 more

Not affiliated with or endorsed by the companies shown.

Find out why Google skips your page, with a fix list

Paste your page's address or source and get the reasons Google may skip it, ranked, with the exact text to paste.

Version 1.0Updated 12 Oct 2026

Needs access to
The web
Permissions
Browses the web
Time to result (our estimate)
3 minutes to set up, 5 minutes a run

Example

Example session

  1. You

    Why doesn't our beans page show up on Google? People would search for things like "fresh roasted coffee beans" or "buy coffee beans online", and locals for "coffee beans Harbour Street". Here is the page source I copied from the browser.

    • beans-page.html
  2. Your AI

    Verdict: the page tells Google to leave it out of search results.

What comes out
MarkdownWhy Google skips the beans page, and the fixesExample output

Why Google skips the beans page, and the fixes

Ten fixes, most important first


Verdict: the page tells Google to leave it out of search results. The line <meta name="robots" content="noindex, nofollow"> does that on its own, whatever else is on the page.

I checked the page source you pasted against your three searches: "fresh roasted coffee beans", "buy coffee beans online" and "coffee beans Harbour Street". Here is what to fix, most important first.

Fixes, most important first

1. Delete the line that hides the page from Google

Impact: High · Time: 2 minutes

  • What we found: the head of the page contains <meta name="robots" content="noindex, nofollow">.
  • Why it matters: "noindex" tells Google not to show this page in results at all, and "nofollow" tells it not to follow the page's links to your other pages, so nothing else on this list can help until the line is gone.
  • Fix: delete that whole line on the live site. Don't replace it with anything: with no robots line, Google treats the page as fine to list. If you edit the site through a site builder rather than the code, look for a setting called something like "hide from search engines" or "discourage search engines" and switch it off for the live site. Keep it switched on for any test copy of the site, so the test copy stays out of Google.

2. Point the canonical link at your live page, not the test site

Impact: High · Time: 5 minutes

  • What we found: <link rel="canonical" href="https://staging.northwind.example.com/shop"> names your staging address (a test copy of the site) as the real version of this page.

  • Why it matters: a canonical link tells Google which address is the main copy of a page, so this one points Google at the test site instead of the page your customers use.

  • Fix: change the address to this page's own live address, exactly as it shows in your browser bar. If that is https://northwind.example.com/shop, the line becomes:

    <link rel="canonical" href="https://northwind.example.com/shop">
    

    This line and the noindex line both look like leftovers from the test site, so check the source of your other pages for noindex and staging. as well.

3. Give the page a title that says what it sells

Impact: High · Time: 5 minutes

  • What we found: the title is <title>Shop | Home</title>, which doesn't mention coffee, beans or Northwind Coffee.

  • Why it matters: the title is usually the blue headline of your result in Google and one of the strongest clues to what the page is about, and "Shop | Home" matches none of your searches.

  • Fix: replace it with:

    <title>Buy Fresh Roasted Coffee Beans Online | Northwind Coffee</title>
    

    That's 56 characters, short enough to show in full in most results, and it contains both "fresh roasted coffee beans" and "coffee beans online". If local customers matter more to you than online orders, use Fresh Roasted Coffee Beans in [your town] | Northwind Coffee instead, keeping the whole title to about 60 characters.

4. Add one main heading (H1) that says "coffee beans"

Impact: High · Time: 10 minutes

  • What we found: there is no H1 (the page's main headline in the code); the first heading is <h3>Our beans</h3> and the coffees are <h4> headings with nothing above them.

  • Why it matters: Google and screen readers use the main heading to understand what a page is about, and "Our beans" on a third level heading never says coffee.

  • Fix: change <h3>Our beans</h3> to:

    <h1>Fresh roasted coffee beans</h1>
    

    Then change each coffee's <h4> to <h2>, for example <h2>House Filter</h2>. Your theme may size the new headings differently; if they look wrong, adjust them in /assets/theme.css.

5. Add words about the coffee

Impact: High · Time: about an hour

  • What we found: the whole page has about 60 visible words, mostly menu labels, prices and "Add to cart", and the word "coffee" appears once, in © 2026 Northwind Coffee.

  • Why it matters: Google matches pages to searches mostly through the words on them, so a page that never describes its coffee in a sentence has very little to match "fresh roasted coffee beans" or "buy coffee beans online".

  • Fix: put a short intro under the new H1. This one uses only what your page already says:

    <p>Northwind Coffee roasts its coffee beans fresh every Tuesday. Buy them online in 250g bags with delivery for $5, free on orders over $40. Or visit our cafes on Harbour Street and at the Old Mill.</p>
    

    Then add two or three sentences under each coffee. Fill in the brackets with what you'd tell a customer at the counter, and write only what's true:

    <h2>House Filter</h2>
    <p>[What it tastes like]. [Light, medium or dark roast], from [where the beans come from]. Good for [filter, plunger or espresso]. [Sold as whole beans or ground.]</p>
    

    For the Single Origin of the Month, one line explaining the monthly pick and naming this month's coffee works well.

6. Put the beans page in the main menu

Impact: Medium · Time: 5 minutes

  • What we found: the menu has Home, Our cafes, Videos and Contact, but no link to the shop (/shop, going by the canonical line).

  • Why it matters: Google finds pages and judges how important they are largely by the links pointing to them, and a menu link usually appears on every page of the site.

  • Fix: add this inside <nav>, after the Home link:

    <a href="/shop">Coffee beans</a>
    

    Use the page's real path if it isn't /shop. I can only see this page's menu, so if your home page already links to the shop in another way, this still helps but matters a little less.

7. Add a meta description

Impact: Medium · Time: 5 minutes

  • What we found: there is no <meta name="description"> line in the head.

  • Why it matters: the description is often the two lines of text under your title in Google, and without one Google picks text from the page, which here could be "Add to cart" or "Click here for more info".

  • Fix: paste this under the title line:

    <meta name="description" content="Fresh coffee beans roasted every Tuesday. Buy online from $15 a 250g bag, free delivery over $40, or visit our cafes on Harbour Street and at the Old Mill.">
    

    It's 155 characters and uses only facts from your page. Google sometimes rewrites descriptions, but it often uses a good one. Update it if your prices or delivery charge change.

8. Write out your cafe addresses, hours and phone number

Impact: Medium · Time: 20 minutes

  • What we found: the only location text is Visit us! Harbour Street and the Old Mill., with no street numbers, town, opening hours or phone number.

  • Why it matters: for searches like "coffee beans Harbour Street", Google looks for a full address it can match to your Google Business Profile (your listing on Google Maps), and a street name alone gives it little to go on.

  • Fix: replace that footer line with your details, written exactly as they appear on your Google Business Profile:

    <p>Visit our cafes:<br>
    Harbour Street: [number] Harbour Street, [town] [postcode]. Open [days and hours]. Phone [number].<br>
    The Old Mill: [street address], [town] [postcode]. Open [days and hours]. Phone [number].<br>
    <a href="/cafes">More about our cafes</a></p>
    

    If the footer is shared across your site, this one change helps every page. If either cafe doesn't have a Google Business Profile yet, setting one up is free and is the main way to appear on Google Maps.

9. Describe your photos with alt text

Impact: Low · Time: 15 minutes

  • What we found: none of the six images has alt text (a short written description of an image, kept in the code), for example <img src="/images/IMG_2077.jpg"> for the House Filter, and the logo link <a href="/"><img src="/images/logo-final-v3.png" width="180"></a> has no words at all.

  • Why it matters: Google relies mostly on alt text to know what a photo shows, so without it your product photos are unlikely to appear in Google Images, and people using screen readers hear nothing for them.

  • Fix: add an alt to each image:

    <img src="/images/logo-final-v3.png" width="180" alt="Northwind Coffee home">
    <img src="/images/IMG_2041.jpg" alt="[what the photo shows, in a few words]">
    <img src="/images/IMG_2077.jpg" alt="House Filter coffee beans">
    <img src="/images/IMG_2081.jpg" alt="Single Origin of the Month coffee beans">
    <img src="/images/IMG_2090.jpg" alt="Espresso Blend coffee beans">
    <img src="/images/IMG_2093.jpg" alt="Decaf coffee beans">
    

    While you're there, renaming the files (for example IMG_2077.jpg to house-filter-coffee-beans.jpg) helps a little more. Update each src to match.

10. Add product details Google can read directly (structured data)

Impact: Low · Time: 30 minutes

  • What we found: there is no <script type="application/ld+json"> block on the page.

  • Why it matters: structured data is a hidden block of code that lists your products and prices in a format Google reads directly; it's optional, but it makes it possible for your results to show prices.

  • Fix: paste this just before </head>. Replace [currency] with your three letter currency code (for example USD, AUD or NZD), and northwind.example.com with your live address if it's different:

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@graph": [
        {
          "@type": "Product",
          "name": "House Filter",
          "description": "250g bag of coffee beans, roasted every Tuesday.",
          "image": "https://northwind.example.com/images/IMG_2077.jpg",
          "brand": { "@type": "Brand", "name": "Northwind Coffee" },
          "offers": { "@type": "Offer", "price": "16.00", "priceCurrency": "[currency]" }
        },
        {
          "@type": "Product",
          "name": "Single Origin of the Month",
          "description": "250g bag of coffee beans, roasted every Tuesday.",
          "image": "https://northwind.example.com/images/IMG_2081.jpg",
          "brand": { "@type": "Brand", "name": "Northwind Coffee" },
          "offers": { "@type": "Offer", "price": "19.00", "priceCurrency": "[currency]" }
        },
        {
          "@type": "Product",
          "name": "Espresso Blend",
          "description": "250g bag of coffee beans, roasted every Tuesday.",
          "image": "https://northwind.example.com/images/IMG_2090.jpg",
          "brand": { "@type": "Brand", "name": "Northwind Coffee" },
          "offers": { "@type": "Offer", "price": "15.00", "priceCurrency": "[currency]" }
        },
        {
          "@type": "Product",
          "name": "Decaf",
          "description": "250g bag of coffee beans, roasted every Tuesday.",
          "image": "https://northwind.example.com/images/IMG_2093.jpg",
          "brand": { "@type": "Brand", "name": "Northwind Coffee" },
          "offers": { "@type": "Offer", "price": "17.00", "priceCurrency": "[currency]" }
        }
      ]
    }
    </script>
    

    If you renamed the photos in fix 9, use the new names here. Then paste your page address into Google's free Rich Results Test (search.google.com/test/rich-results) to check Google reads it correctly. Keep the prices here in step with the page when they change.

Also failed, smaller: the delivery link just says "here" (Click <a href="/delivery">here</a> for more info.), so change it to See our <a href="/delivery">delivery details</a>.; and the page doesn't say what language it's in, so change <html> to <html lang="en">.

What I could not check

The page source can't show these. Google Search Console is free: you prove you own the site once, then:

  • Whether Google has the page at all, and what it last saw. Paste the live page address into the URL Inspection box at the top of Search Console. Once fixes 1 and 2 are live, click "Request indexing". Google still has to visit and process the page again, which can take from a few days to a few weeks.
  • Your robots.txt file, a separate file that can block pages across the whole site. Open https://[your live address]/robots.txt in a browser and look for Disallow: / or Disallow: /shop. The robots.txt report in Search Console (under Settings) shows the version Google fetched.
  • How fast the page loads for real visitors. File names like IMG_2077.jpg often mean photos straight off a phone or camera, which can be several megabytes each and slow on mobile data. The Core Web Vitals report in Search Console shows real visitor speed once the site has enough traffic; until then, PageSpeed Insights (pagespeed.web.dev) tests the page for free.
  • Who links to the page. The Links report in Search Console shows which other sites, and which of your own pages, link to it.
  • Whether your staging site is in Google. Search Google for site:staging.northwind.example.com. If anything shows up, put the staging site behind a password so it can't compete with your live site.
  • How it looks on a phone. The viewport line is right, but the styles live in theme.css, which wasn't in what you pasted. Open the page on your phone and check that the text is easy to read and the Add to cart buttons are easy to tap.

Go deeper: for tracking where you rank over time and checking your whole site at once, OpenSEO (github.com/every-app/open-seo) is an open-source tool you can host yourself or rent. It's a separate tool, not part of this check.

Made with Claude Code · Skill

Fit

About this item

Your page is live but nobody finds it on Google. Paste its address, or its source code, and this skill reads it the way Google does: whether it is allowed in the index at all, whether the title and headings say what the page is about, and whether a phone can use it.

You get a short fix list, most important first, in plain words, with the new title and description written out for you to paste. The example checks a made-up coffee shop page that had a test setting left switched on.

What you get

  • A one-line verdict on the biggest reason Google may skip the page
  • Up to ten fixes ranked by impact, each with the time it takes
  • New title and description text written for the search you named
  • What it could not check, and how to check it for free

Good fit

  • Small business owners whose page does not show up on Google
  • Checking a page before or after a redesign

Not for

  • Site-wide audits of hundreds of pages
  • Rank tracking over time

Who it is for

How to use

How to use it

In Claude

  1. Download the skill zip.

  2. In Claude on the web or the desktop app, open Settings, then Capabilities, and turn on Code execution and file creation. On a Team or Enterprise plan, an owner turns this on first.

  3. Open Customize, then Skills. Choose +, then Create skill, then Upload a skill, and pick the zip.

In Claude Code

  1. Download and unzip the skill.

  2. Move the seo-fix-list folder into your Claude Code skills folder.

    macOS and Linux
    ~/.claude/skills/seo-fix-list/
    Windows
    %USERPROFILE%\.claude\skills\seo-fix-list\
  3. Start a new Claude Code session. It loads the skill when the task needs it.

In ChatGPT

  1. Download and unzip the skill.

  2. In ChatGPT, choose New project in the sidebar.

  3. Open Project settings from the project menu and paste SKILL.md from the seo-fix-list folder into its instructions.

  4. Add the skill's other files (anything in its references or assets folder) to the project. Then chat inside the project.

Same steps in

  • Cursor
  • Codex
  • Gemini CLI
  • GitHub Copilot
  • VS Code
  • Amp
  • Goose
  • OpenCode
  • Junie
  • Roo Code
  • Kiro
  • Letta
  • Manus
  • OpenClaw
  • Hermes
  • Muse
  • Dots
  1. Download and unzip the skill.

  2. Move the seo-fix-list folder into your skills folder.

    macOS and Linux
    ~/.agents/skills/seo-fix-list/
    Windows
    %USERPROFILE%\.agents\skills\seo-fix-list\
  3. Start a new session in your AI tool. It loads the skill when the task needs it.

In Grok

  1. Download the skill zip.

  2. Add the zip in the skills or project settings of Grok.

Trust

What's inside

  • seo-fix-list folder
    • references folder
      • checks.md2.3 KB
    • SKILL.md3.2 KB
First lines of seo-fix-list/SKILL.md
---
name: seo-fix-list
description: Checks one web page for the reasons Google may skip it or rank it low, and returns a fix list ranked by impact, in plain words, with the exact text to paste. Use when the user shares a URL or page source and asks why it does not show on Google, for an SEO check or audit, or how to rank a page.
license: Proprietary. Automation Club members only.
metadata:
  automationclub-slug: seo-fix-list-skill
  automationclub-version: '1.0'
---

# SEO fix list

Check one page and give the user a short list of fixes they can make today, most important first.

Needs access to

  • The webReads

    Fetches the page you name, and its robots.txt, to read the code Google reads

Permissions required

  • Browses the web

    ThroughThe web

Requirements

You bring

  • The address of the page, or its source code pasted from your browser
  • What people would type into Google to find it
  • Optional, to go deeper: OpenSEO (github.com/every-app/open-seo, MIT), self-hosted or rented

Outside costs

  • Optional OpenSEO, hosted, plus its DataForSEO data costs: About $10 a month plus data (our estimate)

Tested on

VerifiedTested in the last 90 days
  • Claude Code · Claude Opus 5.512 Oct 2026 · Run on the pasted source of a made-up shop page, with web fetch off. The live address path is still to be tested.

Known limitations

  • It checks one page from its code. It cannot see whether Google has indexed it, how fast it loads for real visitors or who links to it. It tells you how to check those for free.
  • It never promises rankings. It finds what is in the way and how to fix it.

More

Questions

Do I need any SEO tools?
No. It reads the page's code, which is what Google reads first. Paste the address in a chat that can open web pages, or paste the page source if it cannot.
Will this get me to the top of Google?
No one can promise that. It finds what is stopping Google from showing the page, or making it hard to understand, and tells you how to fix each one.
What if I want rank tracking or a whole site audit?
The fix list ends with a pointer to OpenSEO, an open-source SEO tool by another team that you can host yourself or rent for about $10 a month plus data costs. It is not part of this skill and we do not bundle it.