Skip to main content
Use /seo when you want daoco to review public pages or recommend concrete search improvements.

​
The SEO tab

Open Home, choose Website, and stay on the SEO tab. This is where everything the SEO work produces is kept, so it is there when you come back. The band across the top gives you a site score averaged across your audited pages, how many tracked keywords sit in Google’s top 10, and how often AI answers mention you. Run an SEO analysis starts the first audit and Re-audit repeats it. To repeat the review every week, ask your assistant. Below that are five cards:
  • Pages, weakest first. Hover a page for its content, authority, technical, and AI-readiness scores, when it was last audited, and Fix this page.
  • What to fix, the recorded findings ordered by strength. Each one names the measured signal behind it and, when the page has it, the element it is about in the page’s own words. Choose Fix with daoco to start the run, Copy prompt to take it elsewhere, or Source to open the thread that found it.
  • Content refresh queue, findings about how well a page serves its target query. Each finding shows the model’s judgment, confidence, evidence coverage, and ranking data when available.
  • Keywords, your tracked positions with Check now beside them.
  • Backlinks, what the backlink watch recorded on its last check.
Each page score is four categories that contribute up to 25 points each, for a total out of 100. When Content fit assessments are available, they appear separately from those scores. They judge page relevance, keyword fit, content gaps, and overlap between pages. An uncertain answer is marked not enough evidence. A partially inspected page cannot establish a missing topic, and page overlap alone does not prove ranking cannibalization. In the content refresh queue, choose Re-evaluate to inspect the page again before acting on a finding. Dismiss marks a finding you do not want to pursue; Restore reverses that decision. Fix starts a change through your connected CMS or GitHub. These assessments are model judgments, so review the evidence alongside any measured traffic or ranking data. The Fix actions require a usable CMS or GitHub connection: GitHub, Shopify, Square, Webflow, Wix, or WordPress. A fix opens the connected resource, prepares the exact change, and stops for approval before any write. Without one of those connections, the control reads Connect CMS or GitHub and takes you to Connections instead of starting a run that cannot change the site. You can still copy the recorded fix prompt for use elsewhere. On a connected GitHub repository, a fix that needs engineering judgment is filed as an issue for a maintainer. A fix daoco can author correctly from files it has read can instead become one pull request, opened after your approval. daoco never merges it. See Connect GitHub. If a follow-up names a recorded finding, the SEO agent can look up that exact finding across the brand’s conversations. It checks the saved evidence before handing CMS or repository work to the connected-app agent.

​
What /seo helps you do

  • Audit a single page for SEO issues and prioritized fixes.
  • Compare multiple URLs.
  • Discover important pages from a domain.
  • Research competitor SEO pages and positioning.
  • Find content gaps for a topic, product category, or competitor set.
  • Improve AI search readiness and citability.
  • Review schema, headings, canonicals, meta tags, internal links, and page structure.
  • Crawl the whole site for broken links, redirects, duplicates, and orphan pages.
  • Measure page speed and Core Web Vitals.
  • Check which AI crawlers your robots.txt allows and whether you have an llms.txt.
If an audit stops after announcing the work without a specialist result, daoco makes one more attempt automatically. If the report is still missing, the conversation shows the missing report and the audit step is marked unsuccessful.

​
Audits remember the last one

Every page audit is stored against the page. Re-audit the same URL later and the report leads with what changed since. It gives score movement by category, plus the specific edits behind it: a rewritten title, a canonical that moved, schema types that disappeared, images that lost their alt text. If nothing changed, it says so in one line rather than repeating the scorecard. Two spellings of the same page (with and without www, with a tracking parameter, with a trailing slash) share one history, so a re-audit is a comparison rather than a fresh start. Completed audits open separate SEO audit and Rankings tabs when the brand has recorded rank checks. The rankings tab shows the latest stored positions and their measurement date. Opening an audit does not run a new paid rank check.

​
Site crawls, page speed, and AI crawlers

A full-site or technical audit crawls your site from the homepage and sitemap, up to 150 pages. It reports problems that only show up across pages, and each one names the URLs behind it:
  • broken internal links
  • redirect chains and loops
  • pages only the sitemap knows about
  • duplicate titles, descriptions, and content
  • canonical tags that disagree with the HTTP header
  • noindex pages listed in the sitemap
  • thin, deep, and slow pages
Each crawl is saved, so the next crawl of the same site shows what is new and what was fixed. The crawler reads the HTML your server sends and does not run JavaScript. It follows the audited site’s robots.txt rules as DaocoSEOAudit, including for pages a redirect leads to. Crawls stop when their page or time limit is reached, including during redirects. The report marks coverage as partial; pages left unchecked are not reported as broken. Ask about speed or Core Web Vitals and daoco runs Google PageSpeed Insights. You get Lighthouse scores and lab measurements, plus real-visitor LCP, INP, and CLS when Google has enough traffic data for the page. Ask whether AI assistants can read your site and daoco checks your robots.txt against the AI crawlers from OpenAI, Anthropic, Perplexity, Google, Apple, Meta, Common Crawl, and others. It also checks whether /llms.txt exists and is valid. Blocking a crawler that collects training data is reported separately from blocking the AI search and browsing agents that cite your pages in answers.

​
With Search Console and Analytics connected

Connecting Search Console or Google Analytics changes what an audit can claim. Instead of ranking fixes by severity, it ranks them by the traffic actually at stake, and it can state indexation and ranking as fact rather than inference. Google Analytics and Search Console are available to every workspace. Without either connection, audits work exactly as described above and label anything they cannot verify.

​
Example prompts

Technical audits read the original page HTML: headings, links, images, canonical URLs, and JSON-LD structured data, including the author and published or updated dates it declares. Scripts and framework data are ignored, so a heading counts once however the page is built. An image with empty alt text is treated as decorative, not as missing alt text. Findings fit the page they are about. An audit recognizes home, article, blog index, product, contact or company, and docs pages, and skips advice that doesn’t apply: a contact page is not told to add a comparison table, and only articles are checked for a named author and a publish date. A specific new title or meta description is proposed only when Search Console or keyword data backs it; otherwise the finding says what is wrong and leaves the wording to you. Recorded fixes only target your own site, meaning the website on your brand profile and its subdomains. Competitor and reference pages you ask daoco to audit are used for comparison and never appear in What to fix. If the brand has no website on record, daoco cannot tell which pages are yours and keeps the findings the audit recorded.