Claude SEO is an open-source Claude Code plugin for reviewing a public page’s title, content, and search settings. Start with what the page returns, then use Codex to find where to make a change in the repository. On November 11, we compared the public HTML and sitemap for all three language versions of Park Labs’ BrickQuest award article.
Start with one page
Before scanning the whole site, pick one page where you can say what a reader came to find. For the BrickQuest award note, the first questions are which hackathon it was and what prize the project won. Look for the event and result in the title and opening paragraph, then check for a product link for readers who want to try it. It's easy to muddle a title if you assume someone looking for the product and someone looking for the hackathon result want the same page.
Narrow the audit with Claude SEO
If you're setting up the plugin for the first time, open Claude Code and run these commands one at a time. Once setup finishes, use /seo doctor to check that it's ready. Claude SEO installation guide
/plugin marketplace add AgriciDaniel/claude-seo
/plugin install claude-seo@agricidaniel-claude-seo
/seo setupStart with one article once the plugin is ready. The Park Labs observations below came from the HTML and sitemap retrieved with Codex.
/seo page https://park-labs.com/ko/notes/020/
/seo hreflang https://park-labs.com/ko/notes/020/Use the first command to review the title, content, and page settings. Use the second to follow the links between translations. If the same issue shows up across several articles, widen the scope with /seo audit. To record a before-and-after comparison, run /seo drift baseline and then /seo drift compare for the same URL. Claude SEO command reference
What the three language versions returned
The canonical tag suggests a preferred URL to search engines. The hreflang tags connect language versions of the same article. If the Korean page points to the English page, the English page should point back. Google also asks each version to include itself in the list. Google's guide to localized pages
Table 1 · BrickQuest note in the public HTML and sitemap on November 11
| Page | Canonical in HTML | Language links in HTML | Sitemap |
|---|---|---|---|
| Korean | /ko/notes/020/ | ko, en, ja | Listed |
| English | /en/notes/020/ | ko, en, ja | Listed |
| Japanese | /ja/notes/020/ | ko, en, ja | Listed |
All three URLs returned 200, and each page named its own URL as the canonical. To see which URL Google actually chose, open the indexed version in Search Console's URL Inspection tool. Use the live test in that same tool to inspect the currently deployed page separately. Google Search Console URL Inspection
A prompt for Codex
Use this prompt with your site's repository open. When the AI flags something, get the URL and the actual value so you can decide whether to change it.
Run a read-only check of these public pages on my site and sitemap.xml.
https://park-labs.com/ko/notes/020/
https://park-labs.com/en/notes/020/
https://park-labs.com/ja/notes/020/
For each URL, report the HTTP status, HTML lang, title, robots directives,
canonical, actual hreflang targets and return links, and sitemap inclusion.
For each issue, give the observed value, expected value, evidence URL, and
the source file to change. Mark indexing status as unverified where it
cannot be determined from public HTML. Show the findings before editing files.If all three pages point to the wrong canonical, look for the shared metadata generator before editing three translations. If the event name is missing only from the Korean title, start with that title. At Park Labs, we run pnpm check to validate the static export after editing, then fetch the same public URL after deployment to see whether the value changed.
%% Checking a change from the first URL through deployment · Park Labs workflow
flowchart TD
A["Pick a reader question and URL"] --> B["Use AI to flag possible issues"]
B --> C["Check the public HTML for evidence"]
C --> D["Make the change and validate the build"]
D --> E["Check the deployed URL again"]
E --> F["Check indexing and impressions in Search Console"]Read search data separately
An AI report's score can help decide where to look next. For changes in search results, open Search Console's Performance report. Log the date and URL you changed. Once enough data comes in, compare clicks and impressions over periods of equal length for the same page and query. Seasonality and changes in demand can move those numbers too. Google Search Console Performance report
Suggestions from /seo geo about headings and sources can inform the edit. For Google's AI search features, put verifiable facts like the event name, date, and award near the start. Google recommends following the fundamentals of Search for its generative features as well. This check recorded three URLs, the canonical for each, and whether each appears in the sitemap. Those same three rows can be checked again after the next deployment. Google's guide to generative AI features in Search