MAJR Daily Brief: August 10th, 2026

The SEO service is now AI SEO. The name now says what the service does: search and AI-answer readiness. You'll see the new name in the catalog, on the API docs and in generated SDKs, and on future What's New entries. Published What's New entries keep their original titles, so your feed reader won't re-flag them as unread.

The audit tool description now leads with what it actually measures, rather than implying a full AI-answer readiness verdict.

The service is now called AI SEO. The old name asked you to decode three acronyms to learn it covers search and AI-answer readiness. The new name says it directly. You will see it on majr.app, in the API docs and any generated SDK, in the What's New feed title, and in the package README.

Already-published What's New entries keep their original titles, so your RSS reader won't re-flag them as unread. The feed shows the old name before the rename and the new name after.

Clearer wording on the page audit. The audit_page tool description now opens on what it actually measures instead of naming the product. The audit checks 13 signals; two of them relate to AI readiness, and it does not read your llms.txt or your AI-crawler robots policy. The new wording reflects that scope rather than implying a full assessment.

Clearer service catalog entries. Each service now opens with what it does for you, in one plain sentence, with the detail underneath. Catalog descriptions can carry paragraph breaks, so caveats are easier to read.

More accurate SEO audit description. The SEO audit reads your origin's robots.txt and fetches the canonical target, and the catalog now says so. It reports the block it sees, and it does not claim to know which crawlers honor a directive or who is still indexing you.

Honest scope on two summaries:

• The SEO service makes a page ready for search and answer engines. Whether an engine then indexes or quotes it depends on authority and selection the service does not control.
• Media encoding returns web-ready video, audio, and images.

The audit now looks beyond the page itself. Alongside the page you're checking, it fetches robots.txt and the canonical target so you can see how the surrounding site affects readiness.

More predictable audit runs. Two fetcher waits that could run past the audit's time budget are now bounded, so audits finish within expected limits.