Menu

Individual skill

patent-backed-seo-quick-wins

0upvotes

Use this skill when you're looking at one page and don't know its SEO status, and you want the two or three quick wins worth doing now — each traced to the mechanism behind it, not a hunch. Point it at a single page; it returns a short, ranked list of instant-win actions, and for every action it names the Google patent or leaked Search API field that explains why it works, so you can verify the claim yourself and defend it in a client or sales call. Reach for it when you'd say "what are the quick wins here", "audit this page", "why would this rank", "prove this isn't guesswork", "what does Google actually reward", or "back that with a patent".

skills/thebigasif/patent-backed-seo-quick-wins/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

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 11, 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)
237
Repository last updated
Oct 20, 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

Applies to a single page whose SEO status is unclear and you want the fastest wins. Produces the top two or three quick wins for that page — each traced to the ranking mechanism behind it, with a verifiable patent ID or leaked Search API field as the receipt.

## Bring a direction — the skill grounds it, it doesn't pick it

Come in with a read: "the title is fighting the query", "the content is thin", "nothing internal points at this page". The skill's job is to confirm or kill that read against how the ranking system is documented to work — and to sharpen your model of that system while it does. Hand it a URL with no hypothesis and you get a generic audit any tool spits out. The edge is the direction you bring; the evidence is what makes it defensible.

## Read the page the way the system does

Pull the page and its target query. Walk the elements Google is documented to weigh: the title and how well it matches the query, the headings, the depth and originality of the main content, the internal and inbound anchors, the freshness signals, and the site-level context the page inherits. Mark what's weak — that is your shortlist of candidate wins.

## Every win needs a receipt

For each candidate, name the mechanism that makes it work and attach the evidence: a Google patent that describes the mechanism, and/or a field in the Search API documentation showing Google stores the signal. Read `references/evidence-map.md` for the verified starter set — patent IDs, leaked field names, the on-page action each one grounds, and how to confirm a new one before citing it. A win you cannot tie to a mechanism is a preference, not a quick win: drop it, or label it a hypothesis and say so.
Back to top