What should you prepare?
- The representative domain and key URLs you want to analyze.
- Page groups such as homepage, product pages, newsroom/blog, FAQ, and local pages.
- A place to create development tickets or content tasks.
- A simple table for reporting cause, impact, and next action.
How do you verify the result?
| Check | Good state | Next action |
|---|---|---|
| Critical issues | No crawl blockers, missing core metadata, or major rendering blockers | If present, create development tickets first. |
| SEO foundation | Titles descriptions internal links canonical and sitemap are coherent | Decide content and technical fixes. |
| GEO foundation | Schema FAQ structured body and source candidates exist | Connect to Content Factory and Citation Tracking. |
| Page-level issues | Priority URLs are clear | Start with high-impact pages. |
What commonly blocks teams?
| Problem | Cause | Fix |
|---|---|---|
| “We only want to improve GEO” | SEO and GEO are treated separately | SEO accessibility is the foundation for GEO. |
| Too many issues | The team tries to fix the entire site at once | Start with brand conversion newsroom and local priority pages. |
| Owner is unclear | Metrics are not translated into responsibilities | Robots/rendering/schema are technical; headings/FAQ/body structure are content. |
| The team wants only external content | Official-source readiness is underestimated | Fix owned sources first, then design offsite support. |
Reading order
1. Start with important issues
A high score matters less than whether AI and search engines can read the site at all.
2. Separate SEO and GEO
SEO is the search foundation. GEO is readiness for AI-answer sources. Weak SEO usually makes GEO unstable.
3. Assign roles to pages
Homepage defines the brand, product pages explain value, newsroom pages provide official messages, FAQ answers questions, and local pages provide branch signals.
4. Split work by owner
Developers, content teams, PR teams, agencies, and customer approvers should each get different tasks.
Interpretation patterns from meetings
| Scenario | Interpretation | Report sentence |
|---|---|---|
| Large platform or financial service | Technical SEO and trust pages should be checked before non-brand GEO expansion | “Before expanding non-brand acquisition, we need to stabilize official sources and technical accessibility.” |
| Communications team | Newsroom and official statements need to be usable as AI sources | “For AI to cite official messages, newsroom structure and source signals need improvement.” |
| Local business | Branch URLs and regional FAQ should be separated | “Local recommendation visibility requires branch pages and local question sets.” |
| Global expansion | English pages SSR/CSR schema and hreflang should be checked | “English GEO starts with crawlable category definitions.” |
Next action categories
| Category | Examples | Related doc |
|---|---|---|
| Development ticket | robots sitemap rendering schema canonical | Site Audit |
| Content fix | titles descriptions H2 FAQ internal links | Content Factory |
| Strategy decision | which URL or keyword to fix first | Strategy Map |
| Reporting | weekly improvement and expected impact | Weekly Reports |