SEO Audit
freekmurze/dotfiles
When the user wants to audit, review, or diagnose SEO issues on their site.
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Install Geo Meta Tags Audit
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist geo-meta --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/geo-meta .claude/skills/geo-meta && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .claude/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-metaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist geo-meta --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/geo-meta .agents/skills/geo-meta && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .agents/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist geo-meta --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/geo-meta .cursor/skills/geo-meta && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .cursor/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/geo-meta--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist geo-meta --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/geo-meta .gemini/skills/geo-meta && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .gemini/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist geo-metaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/geo-meta .github/skills/geo-meta && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .github/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist geo-meta --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/geo-meta .opencode/skills/geo-meta && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "geo-meta" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/geo-meta into .opencode/skills/geo-meta/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-meta", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
geo-meta- GitHub stars
- 74k
- Token cost
- ~763 tokens
- SKILL.md length
- 310 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
- Works in 4 steps: Add geo meta tags to region-specific… → Use ISO 3166-2 codes for geo.region:… → Ensure geo.position and ICBM use… → …
- Auditing a regional or local site for geo targeting meta tags
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The skill checks a page's head for geo.region, geo.placename and geo.position meta tags. Google does not use them for ranking, but Bing and smaller search engines may read them as a regional signal. It verifies that geo.region holds a valid ISO 3166-1 or 3166-2 code such as US-CA, that geo.position uses the latitude;longitude format with a semicolon, and that an ICBM tag, when present, agrees with the position.
For fixes, it adds the tags to region-specific pages with consistent coordinates. In code review it flags tags that contradict the site's real target region or that appear without hreflang or LocalBusiness schema. Those two, together with the International Targeting settings in Search Console, remain the main ways to target Google, so geo tags are treated only as a supplementary signal. A reference file holds fuller implementation details and framework-specific guidance.
When your agent uses it
- Auditing a regional or local site for geo targeting meta tags
- Checking that geo.region and geo.position values are valid and consistent
- Targeting Bing or regional search engines alongside Google
Example prompts
- “Check the head of our San Francisco landing page for valid geo meta tags.”
- “Add geo.region, geo.placename and geo.position tags to the England store pages.”
- “Do our geo tags contradict the region we target, and do we have hreflang as well?”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Add geo meta tags to region-specific pages in the
- Use ISO 3166-2 codes for geo.region: country code + region code.
- Ensure geo.position and ICBM use consistent coordinates.
- For Google targeting, prioritise: hreflang (multilingual), LocalBusiness JSON-LD (local businesses), and Google Search Console's…
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are html).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Geo Meta Tags Audit loads about 763 tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 310 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 310 words, ~763 tokens.
Download SKILL.mdSave it as
.claude/skills/geo-meta/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- geo-meta
- description
- Use when auditing locally-focused or regionally-targeted pages for geo targeting signals, particularly on sites targeting audiences through Bing or regional search engines. Note that these meta tags have no documented effect on Google's ranking.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/geo-meta
Geo Meta Tags
While Google does not officially support geo meta tags, Bing and other search engines may use them for geographic targeting. For sites with clear regional focus, they provide a low-effort supplementary signal alongside the primary approaches (hreflang, LocalBusiness schema, NAP consistency).
Quick Reference
- Geo meta tags (
geo.region,geo.placename,geo.position) are not used by Google, but may be read by Bing and minor engines - Prefer hreflang for multi-region/language targeting and LocalBusiness JSON-LD for local business signals
- Include geo meta tags only as a supplementary signal alongside, not instead of, structured data and hreflang
Check
In the page <head>, check for <meta name="geo.region">, <meta name="geo.placename">, and <meta name="geo.position"> tags. Verify: (1) geo.region uses a valid ISO 3166-1/3166-2 code (e.g., US-CA for California, GB-ENG for England). (2) geo.position uses latitude;longitude format (e.g., 37.7749;-122.4194). (3) ICBM meta tag matches geo.position if present.
Fix
- Add geo meta tags to region-specific pages in the
<head>:html <meta name="geo.region" content="US-CA"> <meta name="geo.placename" content="San Francisco"> <meta name="geo.position" content="37.7749;-122.4194"> <meta name="ICBM" content="37.7749, -122.4194"> - Use ISO 3166-2 codes for
geo.region: country code + region code. - Ensure
geo.positionandICBMuse consistent coordinates. - For Google targeting, prioritise: hreflang (multilingual), LocalBusiness JSON-LD (local businesses), and Google Search Console's International Targeting settings.
Explain
Geo meta tags signal a page's geographic focus to search engines. While Google does not use them as a ranking factor, Bing's guidelines reference them for geo-targeting. They are most useful for regional or local sites wanting to signal geographic relevance without significant development effort. They should supplement, not replace, hreflang and LocalBusiness structured data.
Code Review
Check <meta name='geo.region'> for a valid ISO 3166-2 value (e.g., 'US-CA', 'GB-LND'). Verify geo.position format as lat;lon (semicolon separator). Flag if geo tags are present but contradict the site's actual target region. Note if geo tags are used without accompanying hreflang or LocalBusiness schema, which are more impactful.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/geo-meta of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Geo Meta Tags Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Geo Meta Tags Audit this skillthedaviddias/Front-End-Checklist | 74k | — | ~763 | Automated safety check: Pass | MIT | |
| SEO Auditfreekmurze/dotfiles | 1k | 34 repos | ~2.2k | Automated safety check: Pass | None | |
| Google SEO APIsAgriciDaniel/claude-seo | 19k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| SEO Drift MonitorAgriciDaniel/claude-seo | 19k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| SEO Coachakseolabs-seo/seo-coach | 146 | — | ~2.8k | Automated safety check: Pass | None |
Similar skills
Google SEO APIs
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
SEO Optimizer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.
SEO Drift Monitor
AgriciDaniel/claude-seo
Captures baselines of a page's SEO-critical elements, compares later snapshots against them and flags regressions by severity, like version control for on-page SEO.
SEO Coach
akseolabs-seo/seo-coach
Beginner-first SEO coaching for people who want to learn by doing one safe, verifiable step at a time.
Universal SEO Analysis
AgriciDaniel/claude-seo
Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Front-End Checklist npm Package Finder
thedaviddias/Front-End-Checklist
Finds two or three well-maintained npm packages for a Front-End Checklist rule, checks download and release thresholds, and adds them to the rule's frontmatter.
Related
Works with
Categories
Questions about Geo Meta Tags Audit
What does Geo Meta Tags Audit do?
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google). position meta tags. Google does not use them for ranking, but Bing and smaller search engines may read them as a regional signal.
When should I use Geo Meta Tags Audit?
Geo Meta Tags Audit fits situations like: auditing a regional or local site for geo targeting meta tags; checking that geo.region and geo.position values are valid and consistent; targeting Bing or regional search engines alongside Google.
How do I install Geo Meta Tags Audit in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a claude-code`. Or copy the skill folder (skills/geo-meta in thedaviddias/Front-End-Checklist) into .claude/skills/geo-meta in your project. Claude Code loads it when a task matches its description.
How do I install Geo Meta Tags Audit in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a codex`. Or copy the skill folder (skills/geo-meta in thedaviddias/Front-End-Checklist) into .agents/skills/geo-meta in your project. Codex loads it when a task matches its description.
Can I use Geo Meta Tags Audit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill geo-meta -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/geo-meta, .gemini/skills/geo-meta, .github/skills/geo-meta and .opencode/skills/geo-meta in your project.
What does Geo Meta Tags Audit need to run?
SKILL.md names no scripts, command-line tools or credentials: Geo Meta Tags Audit is instructions for the agent only.
Does Geo Meta Tags Audit access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Geo Meta Tags Audit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Geo Meta Tags Audit use?
Geo Meta Tags Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Geo Meta Tags Audit use?
About 763 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
What are the alternatives to Geo Meta Tags Audit?
Skills that share tags, products or a category with Geo Meta Tags Audit: SEO Audit (freekmurze/dotfiles, 1k stars), Google SEO APIs (AgriciDaniel/claude-seo, 19k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars) and SEO Drift Monitor (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Geo Meta Tags Audit?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.