extractability-checklisted

Diagnose whether an AI retrieval crawler can actually see and cite a candidate's web page. Use whenever someone gives a page URL and asks what an "AI crawler sees," whether their page is "citable," "extractable," "visible to AI," "retrievable," or "AI-readable" — or asks why their content isn't getting cited/surfaced by AI answer engines. Fetches the page as a non-JS-executing bot would (raw server HTML) and reports whether substantive content is present pre-hydration, whether facts are front-loaded, dated, and sourced, whether Person/FAQPage JSON-LD exists, and whether headings are questions/topics vs slogans. Routes each finding to the right fix skill in this suite. Diagnostic only — never modifies the site. Trigger even when the user just pastes a URL and asks "how does this look to AI?"
meturley/trail-marker-geo · ★ 0 · Data & Documents · score 70

Install: claude install-skill meturley/trail-marker-geo

# Extractability Check This skill inspects a single web page **the way an AI retrieval crawler sees it** and reports whether the content is extractable and citable. Most AI retrieval bots (the fetchers behind AI answer engines) do **not** execute JavaScript — they read the raw server-rendered HTML of the first response. If the substantive content only appears after client-side JS hydration, those crawlers see an empty shell, and nothing on the page can be cited no matter how good it is. That single check is the most important thing this skill does. ## Hard rules (read first) - **Diagnostic only.** Never modify, submit to, or write anything to the user's site. Only fetch and report. - **Report only what's in the fetched HTML.** Never assume content exists, never infer that "it probably renders fine." If it's not in the bytes you fetched, report it as not visible to the crawler. - **Be honest about scope.** This checks *static-HTML visibility and structure* — what a non-JS crawler can see and how well-organized it is for extraction. It does **not** measure live citation performance (whether a given engine actually cites the page). That requires ongoing engine/citation monitoring, which is out of scope. Say so plainly; don't imply this predicts real-world citation. - **One page per run.** This is a page-level diagnostic, not a site crawl. ## Workflow ### 1. Get the URL If the user hasn't given a full URL, ask for one. You need a single concrete page (not a domain). ### 2.