Search Everywhere: 101 SEO, AEO and GEO Tips, Tricks and Mistakes to Avoid
101 field-tested tips across research, technical SEO, speed, schema, content, links, AEO, GEO and measurement, plus the mistakes that cost traffic.

This post is Chapter 27 of Search Everywhere: The Practical Guide to SEO, AEO and GEO, the free online edition. Chapter and appendix references link to the matching post.
This chapter collects short, practical notes from across SEO, AEO and GEO. Some summarise ideas from earlier chapters; many are tricks that did not fit anywhere else. Read them in any order.
Research
- Search the query before you write. The current results tell you the intent and format Google prefers. If every result is a tutorial, do not write a sales page.
- Mine your support inbox. Every question a customer asks by email is a question someone else types into Google or ChatGPT. Keep a running document of them.
- Use autocomplete with the alphabet. Type “opencart 4 a”, “opencart 4 b” and so on to harvest long-tail suggestions.
- Add “vs” to find comparisons. “turnstile vs” shows what people compare a product with, which gives you comparison article topics.
- Read the PAA tree three levels deep. Expand People Also Ask questions repeatedly; the third level often reveals niche questions no competitor answers.
- Filter Search Console by question words. The regex
^(how|what|why|which|can|does|is)\bturns your query report into an AEO to-do list. - Look for eight-word queries. Long queries in Search Console are the closest thing you have to AI prompts in your own data.
- Check Reddit with
site:reddit.complus your topic. Reddit threads reveal real phrasing and frustrations, and AI assistants cite Reddit often. - Ignore high-volume, off-topic keywords. Traffic that does not match your expertise dilutes your identity and rarely converts.
- Keep a fixed prompt set. You cannot measure AI visibility if your test changes every month.
Technical
- Read your sitemaps like a book. Scrolling through post, author and tag sitemaps is a five-minute content audit.
- Every bot-specific robots.txt group must repeat your disallow rules. A crawler obeys only its most specific group.
- robots.txt blocks crawling, not indexing. Use noindex to keep pages out of results, and let Google crawl them to see it.
- Never canonicalise paginated pages to page 1. Each page lists different content.
- Check “View crawled page” in URL Inspection whenever a page will not index. It shows what Google actually saw.
- Disable JavaScript and reload your page. What remains is roughly what most AI crawlers see.
- Test with curl and a bot user agent. Some firewalls serve challenges to bots; curl reveals it instantly.
- Remove the WordPress generator tag. It helps attackers and does nothing for you.
- Noindex tag archives unless you curate them. On most WordPress sites they are thin duplicates.
- Disable author archives on single-author sites, and noindex guest author archives on multi-author ones.
- Redirect attachment pages to the file or parent post.
- Keep redirect chains to one hop. Update internal links to point straight to the final URL.
- Return 410 for content you deliberately removed and that has no replacement.
- Watch the Crawl stats report monthly. A rising response time is an early warning.
- Start the Search Console BigQuery export now. It only collects data from the day you switch it on.
- Submit your sitemap to Bing too, and enable IndexNow. Bing feeds Copilot and other assistants.
- Check your CDN’s AI bot settings. Some configurations block AI crawlers by default; you may be invisible to AI search without knowing.
- Verify Googlebot by DNS before acting on log data. Many “Googlebots” are scrapers.
Speed
- Read field data before lab data. Real-user Core Web Vitals decide rankings; Lighthouse scores are for debugging.
- Never lazy-load the LCP image. Add
fetchpriority="high"instead. - Set width and height on every image and embed. It is the simplest CLS fix.
- Use facades for YouTube, maps, chat and booking widgets. Show a static placeholder and load the real thing on click.
- Audit GTM twice a year. Tags accumulate; each one costs INP.
- Cache HTML at the edge for logged-out visitors if your platform allows it.
- Serve AVIF or WebP with a fallback. Most modern image plugins do this automatically.
- Preload your main web font and use
font-display: swap.
Structured data
- Use one plugin to generate schema. Two plugins create duplicate, conflicting graphs.
- Connect entities with
@id. A graph beats a pile of separate blocks. - Mark up only what users can see. Hidden ratings or FAQs risk a manual action.
- Set your site name in Yoast and everywhere else. It controls the name Google shows above your URL.
- Add
sameAslinks to every official profile for the organisation and each author. - Use specific types like
ProfessionalService,BlogPostingandSoftwareApplication. - Validate with both the Rich Results Test and the Schema Markup Validator. They check different things.
- Do not expect FAQ rich results. They are limited to authoritative government and health sites. Keep FAQs for readers and answer engines.
Content
- Answer in the first sentence. Then explain.
- Write passages that survive being cut out. Repeat the subject instead of “it” or “as mentioned above”.
- Put a summary box at the top of long articles. Readers, Google and AI systems all use it.
- Phrase some H2s as questions people ask.
- Use real HTML tables for comparisons, never images of tables.
- Number your steps and start each with a verb.
- Include versions and dates. “OpenCart 4.0.2.3” is quotable; “the latest version” is not.
- Add a troubleshooting section to every tutorial. It catches long-tail queries and is full of unique information.
- Give something away. A free extension, template or checklist is information gain no summary can replace.
- Show your own screenshots. They prove first-hand experience.
- Cite primary sources. Link to official documentation for factual claims.
- Keep titles around 60 characters, and keep long, descriptive versions as the H1.
- Refresh before you write new. Updating a page with impressions often beats starting from zero.
- Do not change dates without changing content.
- Mark old tutorials clearly with the version they apply to and a link to the current guide.
- Merge multi-part thin posts into one strong guide.
- Let an expert own every AI-assisted draft. Verify facts and add experience before publishing.
- Avoid vague superlatives. “Blazing fast” cannot be quoted; “loads in 1.2 seconds on mobile” can.
Internal linking
- Link from your strongest pages to the ones you want to rank. Find your strongest pages in the Links report or a backlink tool.
- Use
site:yourdomain.com "topic"to find linking opportunities. - Build hubs with real content, not bare date-ordered archives.
- Link tutorials to the relevant service page. Helpful content should lead somewhere useful.
- Fix orphan pages. If nothing links to a page, search engines assume it does not matter.
- Add heading
ids so you, Google and AI systems can link to exact sections.
Authority and trust
- Put a real photo on every author page.
- Make author bios specific. Books, years, projects and numbers, not adjectives.
- Resolve contradictions on your About page. Inconsistent facts undermine trust with readers and models alike.
- Use a domain email address for business contact.
- Keep name, address and phone identical everywhere.
- Replace unsourced statistics with case studies. “500+ projects” is a claim; a named client with results is proof.
- Label mock-ups as illustrations.
- Write one canonical description of your business and paste it everywhere: site, LinkedIn, directories, llms.txt.
- Check what AI assistants say about you every quarter, and fix the sources of any errors.
Links and mentions
- Link every GitHub README to its tutorial.
- Ask for links on unlinked mentions. It is the highest-converting outreach there is.
- Use Backlink Gap to find sites that link to several competitors. They already link to sites like yours.
- Mark paid and guest-post commercial links
sponsoredornofollow. - Tighten your “Write For Us” policy. Off-topic guest posts with commercial links look like link selling.
- Answer questions on forums without spamming. Link only when your resource is genuinely the best answer, and disclose your affiliation.
- Publish original data once a year. It earns links, mentions and AI citations for years.
- Do not disavow by default. Google ignores most spammy links; disavow only for manual actions or known link schemes.
AEO and GEO
- Ranking is the entry ticket. AI answer engines mostly retrieve from search indexes.
- Cover the fan-out. Map the sub-questions behind each core topic and answer each one somewhere.
- Allow the AI search crawlers you want citations from: OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-SearchBot, Claude-User.
- Blocking Google-Extended does not remove you from AI Overviews. It controls Gemini training and grounding.
- Keep important content in HTML. Many AI crawlers do not run JavaScript.
- Treat llms.txt as a curated summary, not a control. Keep it accurate and in sync with your site.
- Look at which other sources AI cites for your prompts. Those are the places to earn mentions.
- Be present on YouTube. Videos with chapters and full descriptions are cited often.
- Make service pages answerable: what you do, where, for whom, with what evidence and at what price.
- Never hide instructions for AI in your pages. Prompt injection and hidden text are manipulation and get discounted.
- Watch user-initiated AI fetches in your logs. ChatGPT-User, Claude-User and Perplexity-User requests show which pages real people’s questions lead to.
Measurement
- Create an AI Assistants channel in GA4 and put it above Referral.
- Remember that Google AI feature clicks count as organic in both Search Console and GA4.
- Report sample sizes for AI visibility. “14% (56 of 400 runs)” is honest; “14%” alone is not.
- Annotate every site change. Without annotations you will never know what caused a trend.
- Measure each layer on its own terms and report them together. Rankings and clicks for SEO, answers and snippets for AEO, citations and share of voice for GEO.
Previous: How to Diagnose a Traffic Drop and Survive Algorithm Updates
Next: SEO, AEO and GEO Checklists: Technical, Content, Migration and More
All chapters: Search Everywhere: The Practical Guide to SEO, AEO and GEO






