How MaxiMarket works
Audit a live page, understand what keeps machines from reading it, fix it, and keep important pages under watch.
Start as any of
- Anonymous visitorNo account needed. Public audits, with a per-address limit.
- Registered userA free account: Sites, page history, monitoring.
- Coding agentMCP, with an API token from your account.
One audit
From the report
- Act on the reportEveryone
- MonitoringRegistered
- Turn on monitoringfor up to 3 pages
- Scheduled checksa new audit every 7 days
- Changesnew and resolved findings, email for meaningful ones
- Agent loopMCP
- get_fix_brieffindings, expected state, fix
- Agent edits your repositoryin your own environment
- Deployby you or your CI
- run_auditthe same URL again
- Verifiedthe fix is confirmed on the live page
Safe by design
Read-only, bounded, verified.
MaxiMarket reads only what any visitor or crawler could: your page, robots.txt and sitemaps, and a few related resources. Every audit starts with a plain HTTP request; when the HTML shows the page builds or loads its content with JavaScript, the same audit renders it in a browser automatically. If access is blocked, the page is unavailable or it cannot be rendered reliably, the report says so, with no invented findings and no Technical Score.
- No login, no form submissions
- Public addresses only
- Strict time and size limits
- A browser only when needed
- Honest about blocked access
- No score without verified content
What you get
Four ideas, one report.
- Findings
- Technical issues that failed a rule, each with what was checked, why it matters and how to fix it. Warnings first; Info marks smaller or intent-dependent points.
- Observations
- Neutral facts, such as which AI training crawlers robots.txt allows. Never pass or fail, never warnings, never part of the score.
- Technical Score
- Technical Readiness from 0 to 100: the share of applicable, weighted technical checks that passed.
- How the score works
- Audit Standard
- The published, versioned rule set every audit follows, now 2026.4. Each rule states its authority, sources and weight.
- Audit Standard 2026.4
With a free account
Keep important pages under watch.
Add an audit to your account and it becomes part of a Site, with each audited page and its history. Turn monitoring on for the pages that matter; after a fix is deployed, Run audit now confirms it and monitoring continues. When a new Audit Standard is published, monitoring stays on its version until you adopt the new one, and the first audit under it is a new baseline.
For whole websites, Website SEO Audit crawls up to 500 pages of a site. It is one of the advanced tools in MaxiMarket Early Access.Self-service activation is not open yet. The usual usage limits apply.
- Every 7 days
- A new audit of each watched page; up to 3 pages on the Free plan. Pause or stop at any time.
- Like-for-like
- Each check is compared with the previous verified audit of the same page under the same Audit Standard version: new, resolved and still-open findings.
- Never a false regression
- A blocked, unavailable or unverifiable check is shown separately and the previous verified score is kept, never a drop to 0.
- Email for meaningful changes
- A regression, an improvement, lost or restored access, or a new Audit Standard. Turn monitoring emails off in your account.
Fix and verify
You or your agent fixes. MaxiMarket verifies.
Every finding states what was checked, the expected state and how to fix it: do it yourself, hand the Fix Brief to a developer, or let a coding agent work from it. After the fix is deployed, a new audit of the same URL confirms it.
Coding agents connect over MCP with an API token you create under Agent access in your dashboard, or by signing in from apps that support it. Each has its own permissions and can be revoked at any time. The agent calls run_audit, waits with get_audit, reads get_fix_brief, changes your code in your own environment, and audits the same URL again after you or your CI deploy.
MaxiMarket receives page URLs and returns audits and Fix Briefs. It never receives, reads or edits your repository and never deploys. Each Fix Brief tells the agent to change only what the findings require. More about agent access
The MaxiMarket Technical Score
Technical Readiness, measured precisely.
The score measures your page against the technical checks of Audit Standard 2026.4 that apply to it. 74 of the 94 rules are scored; the others are reported but never change the number. Every rule ends with exactly one outcome.
The formula
score = 100 × earned weight ÷ applicable weight
Only scored rules that passed or failed count, each with a weight of 1, 2 or 3. Observations and non-scoring rules never change it.
- Passed
- earns its weight
- Failed
- earns nothing, becomes a finding
- Not applicable
- left out, e.g. Product rules without products
- Could not be evaluated
- left out, never counted as passed
What does a score of 100 mean?
Your page passed every applicable scored technical check in Audit Standard 2026.4: 100% Technical Readiness against this version. MaxiMarket found no scored technical barrier, within the scope of the standard, keeping the page from being correctly reached and understood through the signals it audits. It is not a ranking promise and not a complete SEO assessment; beyond it, visibility depends on relevant, high-quality content and the authority, links and brand signals around it.
Why are some rules not scored?
Some states are legitimate choices, like keeping a page out of search or opting out of AI training. Others are optional conventions. MaxiMarket reports them, but never lowers your score for them.
How are rule weights determined?
Each scored rule has a weight of 1, 2 or 3. The weights are MaxiMarket’s methodology, published with a reason for every rule, so you can see why a check counts as much as it does.
Try it on your page
Audit a page. Get clear answers.
Read-only, about a minute, no signup needed. The report follows the published Audit Standard.