geo-meta SKILL.md skillA
geo-meta from thedaviddias/front-end-checklist is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thedaviddias/front-end-checklist/geo-meta@git:20261004.4b0ddb9Pins git:20261004.4b0ddb9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thedaviddias/front-end-checklist
- Path
skills/geo-meta/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261004.4b0ddb9, committed Oct 4, 2026
- First version recorded
- May 29, 2026
- Size
- 3,049 bytes
- Repository stars
- 74,516
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 1. Add geo meta tags to region-specific pages in the `<head>`: ```html <meta name="geo.region" content="US-CA"> …
Read the whole file at its exact version.
How to install
mdr add thedaviddias/front-end-checklist/geo-meta@sha256:9a8c7caa54eb0919The line at the top of this page pins the label git:20261004.4b0ddb9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mpyxvahzv3w65jr3)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 29, 2026 and Oct 4, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261004.4b0ddb9 latest | 2026-10-04 | 4b0ddb9 | 3,049 B | A | view · diff |
| git:20260529.7c05904 | 2026-05-29 | 7c05904 | 3,055 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3049 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
thedaviddias/front-end-checklist · 74,516 stars · license MIT · pushed 2026-10-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mpyxvahzv3w65jr3 GET https://markdownregistry.com/api/v1/resolve?ref=thedaviddias/front-end-checklist/geo-meta GET https://markdownregistry.com/api/v1/blob/9a8c7caa54eb0919db21ca5e11ce47348fdbbe5711b22cab37a62ce3b761fbe4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.