Individual skill

agentic-seo

Turn a public-facing website into optimized for search engines and generative search engines by using all efficient means

skills/generic-utils/agentic-seo/SKILL.md

Read pinned source

Source commit 0c1bc93fd5124e7a862d61c1b434f32ba8790e3a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
153
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Go over the source code and live site (ask the user) and optimize GEO and SEO according to obvious judgement, but don’t leave out any of these:

- Go to https://schema.org/docs/schemas.html and browse schemas we should use, as well as breadcrumbs, for rich results and JSON-LD content for search engines
- Drive a browser to https://www.seoptimer.com/ and run a free login-less site audit and apply all code adjustments to satisfy and get a top score (has 3 attempts a day, alternative fallback to https://www.seobility.net/en/seocheck)
- Use the Open Graph checker https://www.opengraph.xyz/ to ensure that when sites are sent over social media, Open Graph is optimized per page or important page we are sharing in-app.
- User might have a CDN like Cloudflare that does caching, or any other infrastructural service that we don’t want to conflict with; we can use the browser and ask the user to log in there too for tweaks.
- Run a generic security audit because stuff like immature security headers revealing technologies, stack traces, and console log errors may lower SEO
- Check for llms.txt - and concisely create one if missing.
- Ensure correctly generating sitemap.xml (with entries that won’t lower our score)
- Use a browser driver to go to https://search.google.com/ and ensure the site is listed on Google Search Console as an asset, the sitemap is submitted lately, and inspect any page issues and fix them.
- Adapt keywords per page for the content and highly optimize for specific search queries (best if you consult with the user on what you think is the right set)
- Ensure accessibility, privacy, terms, are applied to high extend (unless the user opts out of privacy/terms) to best results
- Also use LightHouse for page speed insights https://pagespeed.web.dev/analysis
- If the site is on Cloudflare, turn on `Crawler Hints`, otherwise, use IndexNow