Analyzes a public page's SEO tags and returns corrections with exact HTML to add or replace, plus paid products that automate them.
What you can do
The fix_page_seo tool runs the SEO Records correction engine on a public page and returns each correction it would apply: the value, the source it comes from, and the exact HTML tag to add or replace in the page head, covering title, meta description, canonical URL, hreflang, Open Graph and Twitter tags. A second tool, get_automatic_fix_offer, describes the vendor's paid products that apply these corrections automatically on every page, with pricing and what each does.
When to use it
Useful when checking or drafting head-level SEO metadata for a public page and wanting concrete tag-level suggestions rather than general advice. Also relevant if you are evaluating whether to buy automation for applying such corrections site-wide.
Requirements
Remote streamable HTTP endpoint at the provider's API host; no packages, environment variables or headers are declared. The page being analyzed must be publicly reachable.
Before you install
The second tool returns commercial product offers with prices, so expect promotional output alongside technical results. Page URLs you submit are sent to a third-party service. No authentication is declared, so do not assume private or staging pages are protected or supported.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.seorecords%2Fseo-records-corrector/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Runs the SEO Records correction engine (the one inside the SEO Records module) on a public page and returns every correction it would apply: the value, the source it comes from, and the exact HTML tag to add or replace in <head> — title, meta description, canonical URL, hreflang, Open Graph and Twitter preview, JSON-LD structured data, image alt texts, robots directives. Also returns the Google snippet before and after, and the issues left to the author because they touch visible content (missing h1, vague link texts…). Free; the page is read, corrected in memory, and forgotten. Docs: https://seorecords.com/assistants
Parametersurlrequired
get_automatic_fix_offer
Apply the fixes automatically: offer and payment links
Returns the SEO Records products that apply these corrections automatically on every page: the SEO Records module (WordPress, PrestaShop, Joomla, Drupal, custom PHP; from €199/year) and SEO Outpost (the same corrections at the network edge, any hosting; from €199 for a year), with what each does, prices and secure Stripe payment links. Docs: https://seorecords.com/assistants
Parameterslanguage
Version history
1
v1.0.0LatestOct 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.