Audit geographic meta tags on region-specific pages, checking region codes, coordinate formats, and consistency with the intended audience. Use the findings to correct supplementary location signals while keeping language targeting and structured business data as primary approaches.
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.
Run score Not tested
See how to installThis skill reviews geographic meta tags on region-specific pages to check whether they identify the intended region correctly. It examines the region code in geo.region, the place name in geo.placename, and the coordinates in geo.position. It identifies errors and conflicts with the page’s actual target region. If an ICBM tag is present, it also checks that its coordinates match.
Use it when reviewing locally focused sites or pages intended for search engines such as Bing. It helps organize supplementary geographic information alongside hreflang, which identifies language and regional page variants, and LocalBusiness structured data, which communicates business information to machines.
<head> of regional pages and identify missing or incorrect geographic meta tags.”geo.region code format and whether geo.position and ICBM coordinates agree.”An effect on Google search rankings is not documented. Treat use by Bing and other search engines as a possibility, and use these tags to supplement hreflang and structured data. In geo.position, separate latitude and longitude with a semicolon.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
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).
geo.region, geo.placename, geo.position) are not used by Google, but may be read by Bing and minor enginesIn 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.
<head>:
<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">
geo.region: country code + region code.geo.position and ICBM use consistent coordinates.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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.