Product Page SEO
adobe/skills
Optimize AEM Edge Delivery Services commerce product pages for search engine crawling and indexing.
A skill your agent uses when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links…
Install Invalid Links
$ npx skills add thedaviddias/Front-End-Checklist --skill invalid-links -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist invalid-links --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/invalid-links .claude/skills/invalid-links && 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 "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .claude/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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/invalid-linksType 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 invalid-links -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist invalid-links --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/invalid-links .agents/skills/invalid-links && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .agents/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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 invalid-links -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist invalid-links --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/invalid-links .cursor/skills/invalid-links && 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 "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .cursor/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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/invalid-links--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 invalid-links -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist invalid-links --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/invalid-links .gemini/skills/invalid-links && 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 "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .gemini/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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 invalid-linksInstalls 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 invalid-links -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/invalid-links .github/skills/invalid-links && 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 "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .github/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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 invalid-links -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 invalid-links --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/invalid-links .opencode/skills/invalid-links && 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 "invalid-links" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/invalid-links into .opencode/skills/invalid-links/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "invalid-links", 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
invalid-links- GitHub stars
- 74k
- Token cost
- ~806 tokens
- SKILL.md length
- 375 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links…
- Works in 4 steps: For links using… → For elements without href (used as… → For empty href='': either add the… → …
- Auditing a pages link elements for crawlability
- 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
Invalid Links is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links have valid href values.
Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Marketing & SEO, covering Technical SEO. It works with JavaScript. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Auditing a pages link elements for crawlability
- Reviewing JavaScript-heavy SPAs where navigation may not use <a href tags
- Checking that dynamically generated links have valid href values
Example prompts
- “/invalid-links”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- For links using href='javascript:void(0)' or href='#' as navigation triggers
- For elements without href (used as button-like elements)
- For empty href='': either add the correct URL or remove the wrapper
- For href='#' anchors: use meaningful fragment IDs that reference actual page sections (href='#features' where id='features' exists)
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.
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
Invalid Links loads about 806 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 375 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). 375 words, ~806 tokens.
Download SKILL.mdSave it as
.claude/skills/invalid-links/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- invalid-links
- description
- Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use `<a href>` tags, or checking that dynamically generated links have valid href values.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/invalid-links
Fix invalid links
Google can only follow links declared as valid <a href> elements with crawlable URL values. Invalid links — empty hrefs, JavaScript voids, or non-URL content — prevent PageRank from flowing to linked pages and stop Googlebot from discovering those destinations.
Quick Reference
- Invalid
<a>tags (empty href, JavaScript voids, non-URL values) are not crawlable — Googlebot cannot follow them - Links must use crawlable
<a href='...'>elements with valid absolute or relative URLs to pass PageRank and be followed - JavaScript-only navigation (onClick handlers without
href) is invisible to search engine crawlers
Check
Parse all <a> elements on the page. Flag links where href: (1) is empty (href='' or href='#' with no meaningful target). (2) starts with javascript: (e.g., href='javascript:void(0)'). (3) starts with mailto: or tel: — these are valid but not crawlable for page discovery. (4) contains only a fragment identifier that references an anchor not present on the page. (5) is absent entirely (<a> without any href attribute). Report the count per type.
Fix
- For links using
href='javascript:void(0)'orhref='#'as navigation triggers:- Add a real URL as the href value
- Use JavaScript to enhance the navigation, not replace it
- Before:
<a href="javascript:void(0)" onclick="openModal()">View Details</a> - After:
<a href="/products/details" onclick="openModal(event)">View Details</a>
- For
<a>elements without href (used as button-like elements):- If they trigger navigation: add href
- If they trigger actions only: change to
<button>elements
- For empty
href='': either add the correct URL or remove the<a>wrapper - For
href='#'anchors: use meaningful fragment IDs that reference actual page sections (href='#features'whereid='features'exists)
Show full SKILL.md (119 more words)Show less
Explain
Google's documentation states that crawlable links must be <a> tags with an href attribute containing a valid URL. Links with javascript: hrefs, empty hrefs, or no href attribute are not followed by crawlers. This means pages only reachable through invalid links are not discovered by Googlebot, and any intended PageRank flow is blocked.
Code Review
Query all <a> elements in the rendered DOM. For each, extract the href attribute. Flag: absent href, empty string, '#' only, values starting with javascript:, values starting with void. Separately flag <div>, <span>, or <button> elements with onclick navigation handlers that lack a corresponding <a href> — these are not crawlable.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/invalid-links
© 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/invalid-links of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Invalid Links 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 |
|---|---|---|---|---|---|---|
| Invalid Links this skillthedaviddias/Front-End-Checklist | 74k | — | ~806 | Automated safety check: Pass | MIT | |
| Product Page SEOadobe/skills | 197 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Qiaomu SEOjoeseesun/qiaomu-seo | 441 | — | ~2.6k | Automated safety check: Pass | MIT | |
| SEO TechnicalAgriciDaniel/codex-seo | 799 | 2 repos | ~2.4k | Automated safety check: Pass | MIT | |
| SEO Technicalsickn33/agentic-awesome-skills | 47k | 2 repos | ~2.2k | Automated safety check: Notes | MIT | |
| SEO Technicalrampstackco/claude-skills | 945 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Qiaomu SEO
joeseesun/qiaomu-seo
Audit, diagnose, research, plan, implement, experiment on, and verify website SEO across Google, Bing, and AI-search surfaces.
SEO Technical
AgriciDaniel/codex-seo
Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol.
SEO Technical
sickn33/agentic-awesome-skills
Audit technical SEO across crawlability, indexability, security, URLs, mobile, Core Web Vitals, structured data, JavaScript rendering, and related platform signals like robots.txt and AI crawler…
SEO Technical
rampstackco/claude-skills
Run a comprehensive technical SEO audit covering crawlability, indexability, rendering, site architecture, structured data, page experience, security, and internationalization.
Hreflang and International SEO
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
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.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
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).
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.
Related
Works with
Categories
Questions about Invalid Links
What does Invalid Links do?
A skill your agent uses when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links…. Invalid Links is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a page's link elements for crawlability, reviewing JavaScript-heavy SPAs where navigation may not use <a href tags, or checking that dynamically generated links have valid href values.
When should I use Invalid Links?
Invalid Links fits situations like: auditing a pages link elements for crawlability; reviewing JavaScript-heavy SPAs where navigation may not use <a href tags; checking that dynamically generated links have valid href values.
How do I install Invalid Links in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill invalid-links -a claude-code`. Or copy the skill folder (skills/invalid-links in thedaviddias/Front-End-Checklist) into .claude/skills/invalid-links in your project. Claude Code loads it when a task matches its description.
How do I install Invalid Links in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill invalid-links -a codex`. Or copy the skill folder (skills/invalid-links in thedaviddias/Front-End-Checklist) into .agents/skills/invalid-links in your project. Codex loads it when a task matches its description.
Can I use Invalid Links 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 invalid-links -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/invalid-links, .gemini/skills/invalid-links, .github/skills/invalid-links and .opencode/skills/invalid-links in your project.
What does Invalid Links need to run?
SKILL.md names no scripts, command-line tools or credentials: Invalid Links is instructions for the agent only.
Does Invalid Links 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 Invalid Links 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 Invalid Links use?
Invalid Links 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 Invalid Links use?
About 806 tokens (SKILL.md is roughly 3.2k 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.1k tokens, read only when the agent opens those files.
What are the alternatives to Invalid Links?
Skills that share tags, products or a category with Invalid Links: Product Page SEO (adobe/skills, 197 stars), Qiaomu SEO (joeseesun/qiaomu-seo, 441 stars), SEO Technical (AgriciDaniel/codex-seo, 799 stars) and SEO Technical (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Invalid Links?
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.