SEO Agent: Same Eight-Module Rules as Web and CLI
By the SEO Health Team · Last updated: 2026-08-16 · We build the SEO Health checker at aimeetup.center. Methods below come from the product’s page audits, sitemap samples, and GSC export math — not from a claimed Google score.
Table of Contents
- TL;DR
- What an agent is allowed to do
- The same eight-module rules
- How the agent should call the check
- Where this sits next to CLI and paste
- What we see when agents call the checker
- Implementation order
- Failure modes
- Frequently Asked Questions
- Conclusion
TL;DR
Direct answer: An seo agent is a caller that fetches one live URL and applies the same eight-module rules as the web paste and the CLI — title, meta, headings, density, images, links, tech, and speed — then returns traffic lights and a next edit, not a second scoring philosophy.
What you'll learn
- A 46-word definition of an seo agent you can quote in a ticket
- Why the caller must reuse the web and CLI rule list
- What to pass in and what must come back
- How lights become an assigned edit
- Failure modes we refuse to call a pass in August 2026 desk samples
If the URL is already open, run a free page check before you let a caller invent a tenth module. The report only helps once the lights match the paste box.
What an agent is allowed to do
Key Definition: An seo agent is a caller that fetches one live URL and applies the same eight-module rules as the web paste and the CLI — title, meta, headings, density, images, links, tech, and speed — then returns traffic lights and a next edit instead of inventing a second scoring philosophy.
Quick answer: An seo agent fetches one live URL and applies the same eight-module rules as the web paste and the CLI, then returns traffic lights and a next edit, not a second scoring philosophy. Key terms
| Term | Meaning |
|---|---|
| Caller | The process that invokes the same rule list on one URL. |
| Surface | Web paste, CLI, or side panel — a door, not a new exam. |
| Traffic light | Green / amber / red per module instead of one vanity 100. |
| Next edit | The one change the lights name on this URL. (#589) |
People type seo agent when they want a process that can check a page without a human pasting the address every time. That is a caller job. It is not a new exam. It is not a second product with a prettier score.
A useful seo agent answers three questions. Which URL did it fetch. Which of the eight modules are red. What is the next edit a person can ship in the same sitting. If the output is only “the page looks fine,” you still have the original problem.
Key definition, applied
The unit of work is one address. Not a domain average. Not a crawl of pages nobody will fix. You hand the caller a URL, it requests the live HTML, and it scores the same eight modules the paste box already uses. Software can run the fetch. A person still has to edit. Write the findings as module, light, and next edit. If you cannot name the edit, the seo agent is not finished.
The Wikipedia page on intelligent agents is the right plain definition for this job: a system that observes and then acts toward a goal. The goal here is a punch list, not a vibe. An seo agent that observes the HTML and then writes a new rubric has left that definition.
Caller, not a new exam
Web paste, CLI, and a caller are three doors. They are not three tests. The category frame around those doors lives in On Page SEO Tool. The scriptable door is SEO CLI. The human paste door is on-page SEO checker. This page stays on the caller.
We run the same eight-module check on URLs we paste into the web form. When a caller invokes that check, the lights must match. What follows is from those desk samples, not from a score we cannot reproduce.
The same eight-module rules
Walk the modules in the same order the paste box uses. An seo agent that opens on a prose summary and hides a noindex tag is entertaining you.
| Order | Module | Pass when | Fail when |
|---|---|---|---|
| 1 | Title | Unique, intent-true, usable as a title link | Empty, duplicated, stuffed, or off-intent |
| 2 | Meta | Plausible snippet, not a second H1 | Empty, copied from the title, or keyword soup |
| 3 | Headings | One H1, outline a human can scan | Missing H1, skipped levels, token-stuffed H2s |
| 4 | Density | Primary phrase in a readable band | Stuffing, or a page that never states the topic |
| 5 | Images | Real alt text, working files | Filename leftovers, empty alts on content images |
| 6 | Links | Live internal and outbound hrefs | 4xx/5xx targets, orphan CTAs |
| 7 | Tech | HTTPS, indexable, coherent head | Accidental noindex, broken canonical |
| 8 | Speed | LCP is not a blocking story | Hero image or font that stalls the first paint |
Title, meta, headings, density
Title asks whether the document name can become a usable title link. Meta asks whether the description is a plausible snippet. Headings should outline the page. Density is a band, not a quota. An seo agent that tells you to paste the same phrase into every H2 is stuffing wearing a caller.
If the caller cannot name which of those four modules is red, it is summarizing. Summaries are not lights. Demand the module name.
Images, links, tech, speed
Images need real alt text. Links need live targets. Tech covers HTTPS, indexability, and a coherent head. Speed here is hygiene, not a rank forecast. An seo agent that skips dead hrefs because “the copy looks strong” has dropped half the rule list.
schema.org SoftwareApplication is a useful reminder that a checker is a product with a name, a URL, and a declared job. Declare the job as eight modules. Do not declare a ninth “agent score.”
After the caller returns, paste the same URL into a free page check and compare lights. If they disagree, believe the mismatch, not the prettier paragraph.
How the agent should call the check
A finished seo agent is a punch list for one address, not a chat that restates the H1. Sort by light. Fix reds before ambers. Leave greens alone.
What you pass in
Pass the exact URL a person would share: scheme, host, path, and query if the query is part of the document. Do not pass a homepage and hope the caller invents the article path. Do not let the caller “helpfully” collapse http and https into one row without showing the hop.
If you are choosing the scriptable door rather than the caller, that is an SEO CLI question. The rules should stay the same. Only who invokes them should change.
Sharing the report is a separate step. The W3C Web Share API is how a browser hands a URL to another app. An seo agent should be that honest about the address it fetched. Print the request URL. Do not hide it inside a story.
What you must get back
You must get eight module names, a light per module, and one next edit you can assign. JSON is fine. Prose is fine if it still names the module. An seo agent that returns only “improve E-E-A-T” on an on-page pass has jumped pillars.
We do not claim a Google on-page API. We report what the document declared against a written list. If Search Console later disagrees about clicks, believe Search Console for traffic and believe the seo agent for “what did we ship.”
Governance still applies when a caller writes the ticket. NIST’s artificial intelligence pages are the right posture: map the risk, measure the leftover, name an owner. That is not a ranking trick. It is how you keep the caller from inventing a score.
What the agent does with lights
| Light | Meaning | Typical action |
|---|---|---|
| Green | Rule passed | Do not reopen the file for this module |
| Amber | Weak or borderline | Fix after the reds |
| Red | Missing or broken | Fix before you leave the URL |
Treat any single number as a qualitative estimate. If the agent report cannot name the module, you are buying a vibe. An seo agent that files a PDF and never changes the title is theatre.
OECD.AI is policy language for systems that act with limited supervision. Use it as a disclosure posture for the caller: say what it fetched, what it scored, and who edits. Hidden generation of a new rubric is a Trust leak on the report itself.
Where this sits next to CLI and paste
The eight modules are the core. Two adjacent doors sit next to the caller. They are not substitutes.
CLI is the script; the agent is the caller
A CLI is the command a pipeline can hang on a pull request. An seo agent is the process that decides to run that command, read the lights, and open a ticket. If you only needed a script, stop on SEO CLI. If you needed a caller that will not invent modules, stay here.
Do not split the rule list because the invocation was a prompt instead of a flag. Prompt or flag, the exam is the same.
Paste is still the human surface
A person still needs a paste box they can trust. That transactional check is on-page SEO checker. Use it to verify the caller. If the human paste and the caller disagree, the caller is wrong until you can explain the delta.
Run the free page check on the URL you will fix today. Then let the caller repeat that check, not a different one.
What we see when agents call the checker
We do not publish fake customer lift. We do publish the misses that repeat.
A second score invented in prose
In our August 2026 desk samples, the most common miss is a caller that restates the H1, adds a cheerful “82,” and never names a module. The page can be missing a title and still get a paragraph about “solid fundamentals.” The fix is to demand the eight lights. That is why an seo agent starts as a caller of a rule list, not as a writer of a new exam.
CISA’s AI page is a useful reminder that automated systems still need an owner. If nobody can say who edits the red, the caller produced a memo.
Lights that never become an edit
The second miss is a perfect JSON report that nobody opens. The seo agent did the fetch. The team did not. If there is no rewrite in the same sitting, you ran a report, not a check.
A third miss is letting the caller skip eligibility. Title polish on a noindex URL is costume. Tech is still module seven. Do not let prose hide it.
Implementation order
Use this sequence on every address so an seo agent stays a caller.
- Name the exact URL. Confirm scheme and host.
- Invoke the same eight-module check the paste box uses.
- Read lights in order. Stop on tech reds before you rewrite density.
- Assign every red to a person. Write the next edit in one sentence.
- Edit. Re-invoke. Compare the same eight lights.
- Only then schedule the caller on the next URL that shares the template.
If step 5 does not change the HTML, you ran a report, not a check. Keep the punch list next to the tab. Close the tab only when the reds are gone or dated. A useful seo agent prints the request URL on every run so you can prove which address was fetched.
Failure modes
These are page and caller failures, not runtime-reliability sermons.
- A new score per door. The paste box shows three reds. The seo agent writes “looks healthy.” You do not have parity. You have two products.
- Prose instead of a module. The caller never says title, meta, headings, density, images, links, tech, or speed. Demand the names.
- Edit never happens. The JSON is pretty. The template is untouched. The seo agent did its job. The team did not.
None of these are “the model was unreliable.” They are rule-list failures. Fix the URL, or fix the caller.
Frequently Asked Questions
Is this a different product from the web paste?
Bottom line: seo agent: No. It is a caller of the same eight-module rules. If the lights disagree with the paste box, the caller is wrong until you can explain the delta.
Do I need a CLI first?
Bottom line: You need a rule list first. A CLI is the scriptable door. An seo agent is the process that invokes that door. If you cannot name the command, you are not ready to automate the paste.
Can the caller add extra modules?
Bottom line: Not on this pass. Extra modules become a second exam. Keep title, meta, headings, density, images, links, tech, and speed. Adjacent jobs get their own URL.
What should I do with a vanity 100?
Bottom line: Ignore it. Read the reds. An seo agent that only ships a doughnut is optimizing for a screenshot.
When is the caller finished?
Bottom line: When a person can name the next edit and the re-run matches the paste box. A paragraph that never names a module is not finished.
Conclusion
An seo agent is a caller of the same eight-module rules the web paste and the CLI already use. Fetch one URL. Return lights. Name the next edit. Believe the reds. Ignore a decorative 100. Start with a free page check. For the tool frame around those modules, stay on On Page SEO Tool.
About the author — SEO Health Team. Reviewer: William Zhu (GitHub). Published and updated 2026-08-16. Credentials appear only here.