> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mythos.new/publishing/seo/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server. # SEO & AI search > Review how search engines and AI assistants understand your site, then ask Mythos to improve the details or fix supported issues. Use **SEO & AI search** to review how your project presents itself to search engines and AI assistants. The page shows default search details, the public address, and separate technical reviews of your saved draft and published site. Open the project workspace and select **More → SEO & AI search**. > **Note** > > SEO can make a site easier to understand and crawl, but it cannot guarantee > indexing, rankings, or inclusion in an AI answer. Search providers make those > decisions independently. ## Review how your site appears The **Default search appearance** card previews publishing defaults. Pages with their own titles and descriptions keep those values; search engines may also choose different wording. * **Title** — the name of the page or site. * **Description** — a short explanation of what the site offers. * **Icon** — the favicon used in browser tabs and supported result previews. * **Address** — the current published hostname when one is available. Select **Ask Mythos to edit details** to improve the title and description, or **Ask Mythos to edit icon** to replace the favicon. Mythos first asks focused questions based on the current project. Review the proposed answers before you submit them. Submitting the change starts a normal Build, because these details belong to your project. The usual Build credit price applies, and you can review the result in Preview before updating the live site. ## Run an SEO & AI search review #### Open the review Go to **More → SEO & AI search**, choose **Draft** or **Published site**, and select **Check SEO**. The review itself is free and does not change your project. #### Read the findings The draft review checks the exact saved source and its stored homepage HTML when available. The published review checks the public homepage, canonical links, crawler directives, sitemap and JSON-LD against the published version and verified primary domain. Neither review treats missing evidence as a pass. #### Choose what to fix Select **Improve SEO** to start a normal Build in chat with Mythos's built-in SEO skill. You do not need to run a check first. Mythos reviews the current pages and improves relevant metadata, crawler files, links, content and structured data while preserving your design and functionality. **Fix with Mythos** focuses on one finding. You can also ignore a finding that does not apply. #### Review the Build Check the updated Preview. A fix does not change the public site until you open **Publish** and select **Update**. #### Verify the result The panel refreshes its review after a Build while open, or when reopened with an outdated review. You can also select **Check SEO**. Saving a Build does not itself mark an issue fixed; only the new check changes its result. Publish separately, then check **Published site**. ## What the review can help with #### Clear page details Check that titles and descriptions explain the page instead of relying on generic defaults. #### Readable structure Find structural issues that make important content harder for crawlers and assistants to follow. #### Crawler access Review the guidance that tells search crawlers what they may discover. #### Live reachability After publishing, verify that the public site is available for live checks. ## Write useful details Prefer a specific title and a plain-language description. Say what the site is, who it serves, and the main reason to visit it. ```text Title: Flour & Stone — artisan bakery in Portland Description: Small-batch sourdough, pastries, and morning coffee, with weekend pickup ordering. ``` Avoid repeating keywords, making claims the page does not support, or using the same title and description on every page. ## Good to know * **Partly verified** means some checks lack evidence, for example metadata supplied by JavaScript after the initial HTML. It does not mean the site is broken. Expand the finding for its scope. * Checks inspect bounded source and homepage evidence, not every rendered page or search-engine index. A valid JSON-LD syntax check does not establish rich-result eligibility. * In a site rendered by JavaScript, changing page metadata may leave initial-HTML findings open. Mythos explains what remains; a normal SEO improvement does not automatically change your framework. Publishing defaults can also make the published result differ from the draft. * Editors can run checks and Builds. Members with read-only access can view the saved findings. * Typing **Improve SEO** selects the same skill for an ordinary Build. A bare **/seo-review** runs the free check; adding instructions preserves their scope in the Builder. * Search engines and messaging apps may cache older information after an update. * Publish the corrected version, then scan again to verify the live result. ## Further reading Google's [SEO Starter Guide](https://developers.google.com/search/docs/fundamentals/seo-starter-guide) explains the foundations of helping search engines discover and understand a site. Use it alongside your Mythos findings when planning content and navigation improvements. ## Related * [Publish your site](/publishing/publish) — update the public version after a successful Build. * [Custom domains](/publishing/custom-domains) — connect the address your audience will use. * [Writing good prompts](/prompting/writing-good-prompts) — describe the audience and desired result clearly. > Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.