Field Notes.
Technical deep dives, local-search checklists, and field notes from building visibility systems for high-trust businesses.
Choose the task before the article.
Use the flagship gate, inspect the relevant service, or begin with the strongest current measurement guides. The complete Field Notes library remains below.
Review crawl, indexation, rendering, links, structured data, performance evidence, and measurement in one local workspace.
→ImplementationReview technical SEO and AI-search visibility servicesSee the diagnostic, implementation boundary, deliverables, and evidence-first process.
→Austin med spasExplore med spa SEO, websites, and booking measurementA commercial path for Austin aesthetic clinics evaluating local visibility and booking friction.
→Austin law firmsExplore lawyer SEO and intake systemsA commercial path for firms reviewing practice-area visibility, attorney proof, and intake measurement.
→Search measurementBuild a branded versus non-branded Search Console baselineSeparate query, page, position, and CTR evidence before interpreting a visibility change.
→AI-search measurementMeasure AI-search visibility without inventing a scoreTrack access, prompts, mentions, citations, referrals, and outcomes as separate evidence layers.
→Google Search Console AI Performance Report Guide
Use Google Search Console's generative AI performance report to interpret impressions, filters, aggregation, limits, and visibility without inventing clicks or ROI.
AI Crawler Controls: Search, Training, and User Fetches
Compare OpenAI, Google, Anthropic, and Perplexity crawler controls for search, training, user fetches, robots.txt, WAFs, IP ranges, and logs.
Google AEO/GEO Claims in 2026
Audit llms.txt, content chunking, AI rewrites, manufactured mentions, and special schema against Google's current AI-search guidance.
Bing AI Performance: Citations and Grounding Queries
Use Bing AI Performance to audit citations, sampled grounding queries, cited pages, and dashboard limits without calling the metrics rankings.
Google Business Profile Integrity Response Plan
A practical response plan for fake-review spikes, inaccurate Google updates, access problems, and other Business Profile integrity incidents.
Branded vs. Non-Branded Search Console Baseline
Compare queries Google classifies as branded and non-branded without confusing the split with customer identity, attribution, or new demand.
Googlebot’s 2 MB HTML Limit: A Byte-Level Audit
A byte-level technical SEO audit for oversized HTML, truncated resources, JavaScript rendering, and critical metadata placement.
Website Redesign SEO Migration Evidence Pack
An acceptance contract for redesigns that change URLs, templates, tracking, or conversion paths without losing search or lead evidence.
GA4 Data Manager API for Offline Service Leads
A narrow implementation and migration guide for using the Google Data Manager API to send GA4 events from service-business lead systems.
SPA Core Web Vitals in Chrome 151: Soft Navigations
Measure SPA Core Web Vitals across soft navigations in Chrome 151 with feature detection, route identity, field validation, and explicit support boundaries.
Local-Service Lead Attribution Guide
A practical architecture for preserving acquisition context across calls, forms, GBP, ads, qualification rules, and CRM outcomes.
Google Business Profile to GA4 Guide
A current guide to GBP-to-GA4 reporting, aggregate metrics, six-month retention, multi-profile limits, and the downstream evidence it still misses.
Measure AI Search Visibility Without Fake Scores
A repeatable protocol for crawler access, prompt sampling, mentions, citations, referral traffic, qualified inquiries, uncertainty, and evidence boundaries.
Austin SEO Visibility Diagnostic for Service Businesses
A practical SEO, AEO, and GEO diagnostic for finding where Austin service businesses leak local visibility, proof, and qualified leads.
AI Search Readiness for Austin Service Businesses
A conservative checklist for making Austin service-business pages easier for answer engines to understand, test, and cite.
Austin Service Page SEO Architecture
How Austin service businesses can structure service hubs, location pages, proof assets, and Map Pack measurement without thin city pages.
The Local Map Pack Playbook for Service Businesses
How to improve local visibility without breaking guidelines or building thin city pages that create measurement risk.
Texas Real Estate Local SEO Without the Myths
A field guide for real estate teams trying to improve local visibility across sprawling metros without profile spam or compliance drift.
The Local SEO Checklist for Service Businesses
Stop guessing why calls are not showing up. A practical 20-point list for making local visibility measurable.
Why Website Speed Drains Lead Conversion
Service-business sites are often slowed down by images, maps, forms, booking tools, and tracking scripts. Here is what to fix first.
Building-Specific Content Strategy Field Note
An anonymized real estate example showing how building-level pages, one CTA, and call attribution can reduce dependence on broad portal leads.
Data Maturity Assessment for Service Businesses
A practical diagnostic for whether calls, forms, CRM, and reporting can prove which visibility work creates revenue.
Stop Doing House Tours
Why practical education content can produce stronger local lead quality than broad luxury home tours.
The 7-Touch Recruiting Pipeline
A recruiting cadence field note for brokerages that need relevant follow-up, clean tracking, and compliance-aware outreach.
Texas Real Estate Market Dynamics in 2026
The state is still growing, but the housing market is no longer one-way. A practical read for brokers who need to price correctly.
The Texas Cost Stack
A practical breakdown of how Texas property taxes, MUD obligations, insurance, and financing can make similar homes differ by hundreds per month.
Builder Incentives vs. Resale in Texas
How to compete when "monthly payment" is the buyer's benchmark. A playbook for winning against new construction.
Decision guides for the work behind visibility.
Each guide resolves one bounded technical, editorial, measurement, website, or AI-workflow decision and leaves a reviewable evidence artifact.
Crawl and index control
Treat crawling, rendering, canonical selection, and indexing as separate states. Preserve a URL-level receipt for each conclusion before changing templates or requesting recrawls.
- Run a Crawlability Audit Before Diagnosing Indexing
- Build an HTTP Status Inventory for Search-Critical Routes
- Review a robots.txt Change Before Production
- Use a Noindex Directive Release Gate
- Audit XML Sitemap and Canonical Consistency
- Design a Defensible URL Inspection Sampling Plan
- Find Orphan URLs and Assign a Disposition
- Contain Crawl Traps Without Hiding Valuable Pages
- Respond to an Indexing Regression as an Incident
- Build a Crawl and Index Evidence Dashboard
JavaScript search rendering
Make the primary answer, canonical metadata, and crawlable navigation available in the server response whenever practical, then verify what hydration changes for users and crawlers.
- Audit Raw HTML and Rendered DOM Parity
- Make SPA Routes Discoverable Without User Interaction
- Release-Check Lazy-Loaded Primary Content
- Verify Head Metadata Through Hydration
- Detect Client-Side Soft 404s
- Govern Canonical Tags in a Single-Page Application
- Ship Crawlable Internal Links in React Interfaces
- Choose SSR, SSG, or CSR for Search-Critical Pages
- Use a Search Release Gate for a JavaScript Migration
- Triage a Bot-versus-Browser Rendering Incident
Information architecture and internal links
Give each valuable buyer task one accountable canonical owner, then use navigational and contextual links to explain relationships rather than manufacture importance.
- Build a Service-Intent Ownership Map
- Design a Useful Hub-and-Spoke Architecture
- Reintegrate Valuable Orphan Content
- Create a Descriptive Anchor-Text System
- Set an Indexing Policy for Faceted Navigation
- Align Breadcrumb Architecture and Schema
- Design Search Paths for Pagination and Infinite Scroll
- Prune Internal Links Without Damaging Navigation
- Run an Architecture Migration Parity Check
- Report Internal-Link Health Without an Authority Score
Canonicalization and migrations
A canonical is a preferred representative, while a redirect changes the requested location. Coordinate both with internal links, sitemaps, status codes, and content equivalence.
- Choose a Canonical URL Representative
- Control Parameter URL Duplication
- Normalize Host, Protocol, and Trailing-Slash Variants
- Make a Canonicalization Decision for Pagination
- Create a Canonical Plan for Syndicated Content
- Build a Content-Consolidation Redirect Map
- Plan a Domain Move for Search Continuity
- Move Hosting Without Changing Public URLs
- QA Redirect Chains, Loops, and Wrong Destinations
- Monitor Canonical Drift After Release
Structured data and entity clarity
Use schema to describe content and relationships that a visitor can verify on the page. Treat eligibility, validity, and search appearance as separate outcomes.
- Match Google Structured Data to Visible Content
- Build an Organization Entity Graph for a Service Business
- Keep Service Schema in Parity With the Page
- Model Article Authorship With Accountable Evidence
- Make a Publishing Decision for FAQ Structured Data
- Respect Review and Rating Markup Boundaries
- Check Breadcrumb Schema Against Visible Navigation
- Model Multi-Location Entity Relationships
- Audit Structured-Data Drift
- Respond to a Structured-Data Incident
AI search evidence and measurement
Start with ordinary crawl access and supportable public facts. Measure prompts, mentions, citations, referrals, and qualified outcomes as distinct observations with explicit coverage.
- Set an AI Crawler Access Policy by Purpose
- Build a Citation-Ready Public Fact Inventory
- Structure a Service Page for Answer Retrieval
- Map Source Authority for AI Search Claims
- Design a Versioned AI Search Prompt Sample
- Report AI Mentions and Citations Separately
- Measure AI Referral Traffic Without Overclaiming
- Make a Bounded llms.txt Publishing Decision
- Monitor Generative Answer Changes Responsibly
- Build an Executive AI Search Evidence Report
Accessible semantic interfaces
Build with native semantics and keyboard behavior first, then add ARIA only where the interaction pattern requires it. Validate with multiple methods and real task paths.
- Run a Keyboard Navigation Audit for a Service Site
- Define an Accessible Lead-Form Contract
- Review Heading Hierarchy as Content Structure
- Manage Focus After SPA Navigation
- Audit Color Contrast in a Design System
- Write Alt Text for Proof and Process Images
- Design Form Error Identification and Recovery
- Implement a Modal Dialog Keyboard Contract
- Create a Reduced-Motion Interface Strategy
- Use an Accessibility Release Gate for Lead Paths
Google Business Profile operations
Operate the profile as a governed public record. Keep identity, eligibility, categories, locations, hours, and service claims aligned with real-world operations.
- Review Business Profile Eligibility and Naming
- Make a Primary Category Decision for Google Business Profile
- Audit Service-Area Accuracy
- Review Business Profile Ownership and Access
- Reconcile Local Business Facts Across Public Surfaces
- Set an Evidence Standard for Local Landing Pages
- Create a Policy-Compliant Review Request Workflow
- Run a Business Profile Suspension-Risk Review
- Maintain a Business Profile Change Log
- Reconcile Business Profile Performance With Leads
Service-page decision architecture
Build each page around one real buyer decision and one service the organization can deliver. Make fit, process, proof, exclusions, and the next action visible.
- Map the Buyer Task Before Writing a Service Page
- Assign One Intent to One Page Owner
- Create Above-the-Fold Service Clarity
- Document a Service Process With Evidence
- Substantiate Service-Page Proof Claims
- Write Responsible Pricing Language for a Service Page
- Explain Service Areas Without Doorway Pages
- Use an Admission Test for Service-Page FAQs
- Choose the Right Call to Action for the Service
- Run a Service-Page Freshness Review
Editorial research and quality assurance
Define the decision the article supports, collect primary evidence, separate observation from inference, and retain a reviewable claim trail through publication.
- Build a Source Hierarchy for Technical Content
- Prepare a Subject-Matter Expert Interview Brief
- Maintain a Claim-Evidence Ledger for Articles
- Fact-Check Technical Guidance Before Publication
- Review AI-Assisted Drafts With an Evidence Gate
- Create a Content Freshness Risk Model
- Assign Accountable Authorship and Review
- Run a Content Cannibalization Review
- Use an Editorial Prepublication Release Gate
- Create a Postpublication Correction Protocol
CMS and content-platform operations
Model editorial intent, evidence, ownership, and release state explicitly. The CMS should prevent invalid public states and make rollback and audit practical.
- Design a Content Model for Service-Business Websites
- Define an Editorial Workflow State Machine
- Govern Reusable Content Blocks
- Test CMS Preview and Production Parity
- Set CMS Slug and URL Governance
- Control Automatic Redirects on Publish
- Validate CMS Fields That Become Public Claims
- Review CMS Roles and Publishing Permissions
- Design Content Versioning and Rollback
- Run a CMS Migration Acceptance Test
Web performance and Core Web Vitals
Use field data to understand user experience and lab traces to diagnose controllable causes. Measure by route and device context, then protect gains with budgets.
- Use Field and Lab Data Together for Performance Diagnosis
- Investigate Largest Contentful Paint by Phase
- Investigate Interaction to Next Paint
- Find the Root Cause of Cumulative Layout Shift
- Set a Performance Budget for Third-Party Scripts
- Improve Image Performance Without Losing Proof
- Create a Web-Font Loading Strategy
- Measure SPA Soft-Navigation Performance
- Set Route-Level Performance Budgets
- Monitor Performance Regressions After Release
Search Console analysis
Define the property, search type, filters, dimensions, date window, and known reporting limits before interpreting clicks, impressions, CTR, or position.
- Document Search Console Data Scope and Lag
- Build a Page–Query Ownership Matrix
- Segment Branded and Nonbranded Search Demand
- Estimate CTR Opportunity Without Traffic Promises
- Analyze Search Position as a Distribution
- Account for Anonymized Search Queries
- Create Reproducible Search Console Regex Filters
- Annotate Search Performance Changes
- Triage a Search Traffic Drop
- Build an Executive Search Performance Report
GA4 event and acquisition design
Start from a business action and an event contract. Collect the minimum useful non-personal context, verify accepted outcomes, and reconcile browser events with operational systems.
- Build a GA4 Measurement Plan From Business Actions
- Choose GA4 Key Events Responsibly
- Define a Form Submission Event Contract
- Define a Call Tracking Event Contract
- Measure a Cross-Domain Booking Flow
- Govern Campaign Parameters
- Measure Page Views in a Single-Page Application
- Set Boundaries for Server-Side Measurement Protocol Events
- Design Analytics Event Deduplication
- QA and Debug a GA4 Implementation
CRM and revenue attribution
Agree on lifecycle stages and source precedence before joining systems. Preserve raw observations, prevent silent overwrites, and report unattributed outcomes honestly.
- Define a Lead Lifecycle Stage Dictionary
- Capture Acquisition Source at Intake
- Compare First-Touch, Last-Touch, and Assisted Views
- Plan an Offline Lead Outcome Import
- Resolve Duplicate Leads Without Losing History
- Code Lead Qualification Outcomes
- Account for Pipeline Lag and Cohort Maturity
- Audit CRM Source Overwrites
- Reconcile Analytics and CRM Lead Totals
- Build a Revenue Attribution Evidence Report
AI workflow discovery and scoping
Choose a narrow task with representative inputs, observable outputs, an accountable exception owner, and a measurable baseline before selecting a model or building an integration.
- Choose a Bounded Task for an AI Workflow
- Write an AI Workflow Input–Output Contract
- Baseline the Manual Workflow Before Automation
- Inventory Exceptions Before Building an AI Workflow
- Design Human Review for AI Output
- Authorize Source Data for AI Workflows
- Design a Bounded AI Workflow Pilot
- Estimate AI Workflow Value Without Fantasy ROI
- Use a Production Admission Gate for an AI Workflow
- Decide When to Sunset or Redesign an AI Workflow
AI automation reliability and evaluation
Constrain outputs and side effects with schemas, permissions, idempotency, evaluation, observability, and explicit escalation. Fail closed when correctness cannot be established.
- Design a Strict Structured-Output Schema
- Define a Safe AI Tool Contract
- Set Retry and Timeout Policy for AI Workflows
- Use Idempotency for AI-Triggered Actions
- Build a Representative AI Evaluation Dataset
- Check AI Output for Unsupported Claims
- Create a Human Escalation Path for AI Failures
- Design Observability for AI Workflows
- Manage Model and Prompt Changes
- Respond to an AI Workflow Incident
AI governance and vendor evaluation
Classify the use case, data, affected people, decision impact, vendor dependencies, and reversibility before approval. Record what evidence supports the decision and what remains unknown.
- Review an AI Vendor’s Data Handling
- Design Model Access Boundaries
- Set AI Data Retention and Deletion Policy
- Run a Security Review for an AI Integration
- Assign a Risk Tier to an AI Use Case
- Define Minimum Documentation for an AI System
- Create an AI Approval and Exception Matrix
- Plan Adversarial Testing for an AI Workflow
- Monitor Material AI Vendor Changes
- Create an AI Vendor Exit and Portability Plan
Conversion and lead-path quality assurance
Test the complete path from landing context through validation, handoff, receipt, routing, and operational disposition. A visible click is not a completed business outcome.
- Set a CTA Hierarchy for Service Pages
- Reduce Form Friction Without Losing Qualification
- QA Lead-Form Error States
- Design a Verifiable Lead Confirmation and Receipt
- Test Phone Routing End to End
- QA a Third-Party Booking Handoff
- Place Consent and Privacy in the Lead Path
- Run Mobile Lead-Path QA
- Test Conversion Paths for Keyboard and Screen Readers
- Monitor Lead Paths Continuously
Evidence-led operating cadence
Separate shipped work, verified system state, external outcomes, and unknowns. Give every decision one owner, evidence window, next action, and stop condition.
- Build a KPI Tree From Visibility to Revenue
- Run a Weekly Website Growth Review
- Maintain an Experiment and Change Log
- Keep an Evidence Register for Cross-Functional Work
- Prioritize Work by Impact, Confidence, Effort, and Risk
- Create a Cross-Functional Ownership Ledger
- Put Evidence Boundaries in an Executive Dashboard
- Write a Decision Memo From Mixed Evidence
- Plan a Quarterly Search and Website Program
- Run a Stop–Start–Continue Review for Growth Work