Field notes.
Not opinions.
Everything on this page is written from inside live engagements — what we watched change, what we shipped, what broke, and what compounded. If it isn't grounded in work, it isn't published.
How to rank in AI Overviews: the 2026 playbook
Semrush shows 720 monthly searches for this exact question and rising. Here is the exact citation-earning playbook we ship in engagements — the entity graph, the first-100-words rewrite, the schema stack, and the tracking cadence.
- ·Citations over rankings.
- ·Entity graph matters.
AI search optimization: the complete 2026 guide
AEO, GEO, LLM-SEO — the labels multiplied faster than the practice.
Dallas SEO: How we increased organic clicks by 214% in 6 months
A deep dive into the 'Dallas Growth engine' we built for a multi-location service brand.
The 2026 Local SEO checklist: How we fix CTR and indexing issues
A prioritized framework for closing content gaps and reclaiming clicks based on our internal audit of over 150 local service markets.
Technical SEO monitoring: Verifying crawl and index status at scale
Why wait for GSC updates? How we set up real-time indexing alerts and crawl monitoring for multi-location brands.
A running log of live engagements, not a content calendar.
This blog exists because most SEO commentary is written at a distance from the work — screenshots of algorithm updates, secondhand summaries of someone else's case study, predictions dressed up as findings. Ours isn't. Every post here traces back to a client account, an internal audit, or a test we ran on our own properties before recommending it to anyone else.
It's written for three overlapping audiences: in-house marketers who need a second opinion before committing budget, agency operators who want to see how a competitor thinks about a problem, and business owners who want proof that the person doing their SEO actually understands the mechanics rather than repeating vendor talking points.
The categories on this page — AI search, technical SEO, local SEO, content, and case teardowns — aren't arbitrary tags. They map directly to the disciplines we staff for on client accounts, so a category filter here is effectively a filter on "what kind of work generated this observation".
How we research and publish
- Sourced from real accounts
Every claim is checked against Search Console, GA4, log files, or a rank-tracking export before it's written down. If we can't point to the data, we don't publish the claim.
- Named authorship
Posts carry the byline of the practitioner who did the work, not a house pseudonym. You can trace a post back to a person and a track record.
- No manufactured statistics
We don't invent percentages to make a headline punchier. If a number appears, it came from a dashboard, not a guess.
- Dated and revisited
Every post is timestamped, and posts affected by a confirmed algorithm or SERP-feature change get revised with a visible update date rather than being quietly rewritten.
- Competing views included
Where the industry genuinely disagrees — attribution models, canonical crawl-budget theory, or how much AI Overviews cannibalise clicks — we say so instead of pretending consensus exists.
If you're new here, read in this order
The blog isn't sequential the way a guide is, but readers new to Optimize Plus tend to get the most value by moving from context to mechanics to proof:
- Step 1 — Orientation
Start with the AI search category to understand how AI Overviews and generative answers are changing what "ranking" means before you dig into tactics.
- Step 2 — Mechanics
Move to technical SEO and local SEO posts, which tend to be the most actionable and the easiest to apply directly to your own site this week.
- Step 3 — Proof
Finish with the case teardowns, which show the mechanics from steps one and two applied together on a real account, warts included.
Blog posts, guides, and services aren't separate silos
A blog post is usually a single thread pulled out of a broader pillar guide or a live service engagement. When a post references a technique in depth, it links through to the relevant pillar guide for the full operating manual, and to the service page where that work is actually delivered for clients. The glossary handles the vocabulary layer underneath both — if a post uses a term you don't recognise, it's almost certainly defined there with an example.
Read together, the three sections form a stack: glossary for definitions, guides for the full method, blog for how the method behaves in the field.
What readers get wrong about a blog like this
- “Frequent publishing means better SEO for the agency itself.” Cadence is a byproduct of client work, not a growth-hacking schedule — we won't publish filler just to hit a number.
- “Older posts are automatically outdated.” Foundational mechanics — crawling, indexation, internal linking — change slowly; only the SERP-feature-specific posts need frequent revision.
- “A case teardown proves the tactic will work for everyone.” A single account's result is evidence, not a guarantee; we flag context (industry, starting authority, budget) precisely so you can judge fit.
- “AI-search posts are hype.” AI Overviews already appear on a meaningful share of commercial queries in our client data; ignoring the category isn't a neutral choice, it's a bet.
Questions readers ask about the blog
- How often does Optimize Plus publish new field notes?
- We publish when an engagement produces something worth reporting, not on a fixed calendar. Most months bring two to four new posts; a quiet month means nothing changed worth writing up, not that we've gone dark.
- Are these posts written by the people doing the work?
- Yes. Every article is written or reviewed by the strategist or engineer who ran the engagement it describes. We don't outsource field notes to generalist copywriters, because the value is in the specificity.
- Do you update old posts when the guidance changes?
- We do. Search evolves quickly enough — especially around AI Overviews and GEO — that guidance from twelve months ago can mislead. Updated posts carry a revised date; we don't silently rewrite history without a note.
- What's the difference between the blog and the guides section?
- The blog is narrow and timely: one experiment, one finding, one client situation. The guides are broad and durable: full operating manuals meant to be referenced repeatedly across a project's lifetime.
- Can I use these posts to do the work myself?
- Many readers do exactly that, and we write with that in mind. We're not withholding the mechanics to force a sales conversation — if you'd rather have us execute it, that's a separate decision.
- Do you cover failures as well as wins?
- Deliberately, yes. A tactic that underperformed on a client site is often more useful to a reader than another success story, because it tells you where the edge cases are.
- How do you decide what counts as a category on the blog?
- Categories map to the disciplines we actually staff for — AI search, technical SEO, local SEO, content, and case teardowns. We don't create a category until we have a sustained body of real work behind it.