How to Run a Search Engine Audit Before Acquiring a Website

A technician checks connected server equipment, highlighting the infrastructure a buyer may need to verify in a website acquisition.
Table of Contents

A search engine audit before an acquisition should establish whether a website’s visibility produces verifiable earnings, whether that visibility can survive a transfer and what it will cost to maintain. A ranking chart alone answers none of those questions.

The deliverable is a buyer’s evidence file: confirmed revenue sources, technical liabilities, transferable assets, AI search exposure and a remediation budget. Use those findings to support the price, require closing conditions or decline the deal. The priority is protecting the earnings you are buying, not maximizing an automated health score.

1. Define the assets and secure evidence access

Establish exactly what the transaction includes. A domain, its content and its operating business are different assets. Rankings may depend on photographs, supplier relationships, booking systems or business profiles that are excluded from the purchase.

Request read-only access where possible and obtain permission before crawling heavily or testing forms. Your evidence set should include:

  • Google Search Console, including performance, indexing, manual actions and security reports.
  • Analytics and conversion definitions, with a history of tracking changes.
  • Order, booking or CRM records sufficient to reconcile organic acquisition with revenue.
  • CMS, hosting and domain inventories, plus relevant plugin and content licenses.
  • Historical SEO reports, migration records and documentation of purchased links or outsourced content.

Use anonymized exports when customer-level data is unnecessary. An acquisition review does not justify unrestricted access to patient, guest or customer information.

Scope the search engine audit around the site’s architecture. A hotel group needs location and booking-path checks; WooCommerce requires product, category and filter analysis. For a large site fleet, sample every important template and investigate anomalies rather than assuming one installation represents all properties. Record who supplied each dataset and when it was exported.

2. Reconcile organic traffic with actual earnings

Ask for at least 16 months of Search Console history and 24 months of analytics and financial records where available. Longer records help reveal seasonality, but missing history should remain an explicit evidence gap.

Compare organic landing-page sessions with inquiries, bookings or orders. Then reconcile those conversions with operational records. Search Console clicks and analytics sessions measure different things, so disagreement is a prompt to investigate, not automatic evidence of manipulation.

Check whether conversion events fire on completed transactions or merely on button clicks. Review refunds, cancellations, duplicate leads, spam submissions and test orders. For e-commerce, separate revenue from contribution after fulfillment, returns and other variable costs.

A search engine audit should challenge the seller’s attribution assumptions. In a hypothetical example, analytics reports 80 organic inquiries, but the CRM contains only 45 matching records and 18 qualified opportunities. Underwrite the reconciled pipeline, not the dashboard headline.

Also identify revenue credited to organic search after earlier paid or offline interactions. That revenue may be legitimate, but attribution does not establish that rankings alone created it. Document the attribution method used in the seller’s earnings calculation and retain the supporting exports for post-close comparison.

3. Separate durable demand from temporary exposure

Use the search engine audit to distinguish business demand from visibility that may disappear independently of ownership. Split performance by brand versus nonbrand searches, landing-page group, country and device.

Classify the query data Search Console exposes, but do not assume visible query rows represent every click. Privacy filtering and reporting limits leave some searches unclassified.

Compare equivalent seasonal periods, not just the latest month against the previous one. For a travel website, a summer peak is not evidence of permanent growth. For an MSP, a cybersecurity incident can temporarily inflate traffic to an informational article without increasing qualified leads.

Measure concentration across the top pages, products and query groups. If one comparison page generates a large portion of organic profit, inspect its ranking history, content rights, conversion path and dependence on a particular partner.

Overlay major releases, outages, migrations and documented search updates on the timeline. Timing can suggest a hypothesis, but it does not prove causation. Request the seller’s change log before accepting explanations for sudden gains or losses. A site with diversified, verified revenue can justify a different risk assessment from one dependent on a single unstable page.

4. Run the technical search engine audit

Crawl the site and compare the results with XML sitemaps, Search Console indexing reports and revenue-producing landing pages. Each source reveals a different population; none is a complete inventory alone.

Start with commercially important templates. Confirm that valuable URLs return the intended status, expose their main content in rendered HTML and use sensible canonical tags. Inspect robots.txt, noindex directives, redirects, pagination and internal linking.

Look for orphaned pages, redirect chains, broken navigation and parameter combinations that generate unnecessary URLs. On WooCommerce, filters can create extensive duplication; on multi-location sites, inconsistent templates can hide entire location groups.

A robots.txt block does not reliably remove an already indexed page. A noindex directive must be accessible to be processed. These distinctions matter when estimating whether a proposed fix will work.

Review the seller’s Google manual actions report and security notifications directly rather than accepting screenshots. A clean report does not prove that all ranking risk is absent, but an unresolved action requires a documented remediation plan.

For every material defect, retain affected URLs, the observed response and the business consequence. “Canonical error on booking pages” is actionable evidence. “Technical score: 62” is not a sufficient basis for pricing the acquisition or estimating repairs.

5. Test performance and complete customer journeys

Test the mobile paths that produce money: booking a room, requesting an MSP consultation, scheduling an appointment or checking out. Include third-party booking engines and payment steps within the review’s authorized scope.

A fast homepage cannot compensate for an unavailable reservation form. Check validation errors, confirmation messages, call routing and whether analytics records successful completion only once.

Within the search engine audit, distinguish field performance from laboratory diagnostics. Google’s Core Web Vitals guidance defines good thresholds as Largest Contentful Paint at or below 2.5 seconds, Interaction to Next Paint at or below 200 milliseconds and Cumulative Layout Shift at or below 0.1, assessed at the 75th percentile.

Use available field data to understand real experiences and lab tests to investigate causes. Passing these thresholds does not guarantee rankings or conversion improvements.

Also test keyboard navigation, form labels, consent behavior and accidental exposure of personal information. Accessibility and privacy deserve acquisition scrutiny without being presented as universal direct ranking factors. Record the defect, customer impact and remediation owner.

Confirm whether performance depends on a hosting arrangement, CDN account or developer-controlled service that will actually transfer to the buyer.

6. Verify content quality, entities and ownership

Inspect a sample covering the highest-earning pages, recently published content and weaker template groups. Check whether titles, headings and body copy answer the intended query and accurately describe the offer.

A search engine audit should also establish who owns the material. Request evidence for commissioned articles, photography, product descriptions, testimonials and syndicated content. A license that permits the seller’s use may not permit transfer to a buyer.

Evaluate whether the site clearly identifies its entities: the business, individual locations, products, services and relevant authors. Consistent names, contact information and relationships help search systems and readers understand what the business actually provides.

Compare structured data with visible content. Organization, LocalBusiness, Product and other schema types should describe real, current facts. Valid syntax alone does not make a claim accurate or establish eligibility for enhanced search presentation.

For healthcare and other sensitive subjects, verify named reviewers, credentials and review processes. Do not treat an author box as proof of expertise.

Finally, identify content that relies on the seller personally. If their reputation, credentials or participation drives trust, document whether that support continues after the transaction and what replacement would require. Include those obligations in the commercial discussion.

Use backlink data to identify patterns, then manually inspect material referring pages. Tool-generated toxicity labels are screening signals, not proof that a link is harmful.

Review anchor text, relevance, placement and recent gains or losses. Determine whether important links come from independent editorial references, paid placements, seller-controlled websites or commercial partnerships.

The search engine audit should flag dependencies that may disappear at closing. A link from the seller’s other business is not a durable asset unless its continuation is agreed. The same applies to directory listings maintained under accounts outside the transaction.

Review historical versions of the domain for unrelated industries, expired-domain repurposing and unexplained language changes. Ask for previous domains and redirect arrangements that still contribute traffic.

Check for trademark conflicts and ownership disputes with appropriate legal support. Search data cannot resolve intellectual-property rights.

Avoid demanding a blanket disavow file as routine cleanup. Removing or disavowing links without evidence can create additional risk. Where suspicious acquisition tactics are material, seek specialist review and price the uncertainty rather than assuming a quick fix. Preserve the source exports so later link losses can be distinguished from ordinary reporting changes.

8. Establish an AI search baseline

Include AI exposure in the search engine audit because buyers increasingly encounter recommendations before visiting a website. Generative Engine Optimization (GEO) focuses on visibility within generated answers; Answer Engine Optimization (AEO) focuses on making useful answers discoverable and understandable.

Test realistic purchase, comparison and local-intent prompts across ChatGPT, Google AI Overviews, Gemini, Perplexity, Claude and Copilot. Record the prompt, date, location context and available model or product details. Note whether an AI Overview actually appears.

Separate brand mentions, linked citations and recommendations. A cited article does not necessarily mean the engine recommends the business. Check whether descriptions, locations and service claims are accurate, and whether cited pages belong to the acquired asset.

Define share of voice before reporting it. For example, count each tracked brand once per answer, then divide your brand’s mentions by all tracked-brand mentions. Ten out of 50 equals 20% within that sample, not across the entire market.

Repeat a fixed prompt set because answers vary. CapstonAI can track mentions, citations and competitor visibility; its baseline complements, rather than replaces, revenue verification. Follow a consistent method to check visibility across Google and AI engines.

Inspect crawler access and content clarity before adding special files. Google’s AI features guidance does not require special AI schema. Treat llms.txt as an optional convention, not a guaranteed indexing or citation mechanism.

A buyer and adviser compare website revenue records and a URL inventory during a search engine audit before acquisition.

9. Verify local coverage and operational dependencies

For multi-site acquisitions, reconcile location pages with real operations. Check addresses, service areas, telephone numbers, opening hours and booking destinations against records the seller can substantiate.

A local-service website such as Junk Auto Car’s Georgia junk car removal site illustrates the questions to ask: which advertised communities are served, where inquiries are routed and whether the buyer acquires the operating relationships behind those pages. This example does not imply that the business is for sale.

For hotels, verify that each property page routes to the correct booking inventory. For franchises, establish which locations, brand permissions and local profiles are included. For healthcare groups, confirm that provider and appointment information remains accurate after closing.

Review eligibility and transfer requirements for business profiles rather than assuming every listing can change hands without qualification. Check ownership of call-tracking numbers and access to historical lead records.

The search engine audit should identify every gap between the website’s advertised footprint and the assets being transferred. Traffic from a city page has limited acquisition value if the buyer cannot fulfill the service or retain its inquiries. Assign an owner to resolve each discrepancy before closing.

10. Match tools to questions, then validate manually

No single platform can verify technical condition, financial attribution, content rights and future visibility. Assemble a small evidence stack around the questions that could change the deal.

Evidence source Useful for Requires separate validation
Search Console Search clicks, indexing and manual actions Revenue and transfer completeness
Analytics and CRM Acquisition paths and recorded conversions Attribution accuracy and lead quality
Site crawler Status codes, canonicals and internal links Business importance of each defect
PageSpeed Insights Field and lab performance signals Real booking or checkout completion
AI visibility tracking Mentions, citations and competitors Answer accuracy and attributable demand

Record findings as confirmed, suspected or unverified. For a crawler alert, inspect representative URLs and determine whether the behavior is intentional before assigning a repair cost.

A search engine audit becomes decision-ready when every material finding has evidence, affected assets, a plausible business effect and a proposed verification test. Separate a reproducible checkout failure from a speculative concern about ranking volatility. Both may matter, but they should not receive the same confidence label or automatically trigger the same purchase-price deduction.

11. Translate findings into acquisition economics

Separate one-time repairs, recurring operating costs and unresolved downside. Ask the team expected to perform the work for scoped estimates, including dependencies and acceptance criteria.

A search engine audit should adjust the earnings model where necessary, not merely create a post-close task list. Unlicensed content may require replacement; unsupported plugins may require ongoing maintenance; nontransferable links may weaken the acquisition thesis.

Consider this hypothetical calculation, using an illustrative multiple rather than a market benchmark:

Valuation input Amount
Seller-stated monthly profit $6,000
Additional recurring monthly maintenance $500
Buyer-normalized monthly profit $5,500
Illustrative valuation multiple 30 months
One-time remediation $9,000
Illustrative adjusted value $156,000

The calculation is $5,500 × 30 − $9,000. It demonstrates how verified costs affect price; it does not establish what the website is worth.

Do not deduct the same recurring expense twice. Keep revenue downside scenarios separate from known repair costs, and label assumptions clearly. A problem may justify a price change, a seller-funded fix, an escrow arrangement or declining the deal, depending on professional advice and transaction terms.

Prioritize by commercial consequence. Broken booking paths and unresolved ownership usually deserve attention before cosmetic metadata inconsistencies. An uncertain claim of future AI traffic should not offset a verified liability in the purchase model.

12. Set closing conditions and verify the handover

Before closing

Require a documented asset and access schedule covering the registrar, DNS, hosting, CMS, analytics, Search Console, relevant business profiles and paid services. Confirm which licenses transfer and which must be repurchased.

Have appropriate advisers address representations, unresolved liabilities and any holdback or remediation obligations. Material access gaps should not quietly become assumptions in the buyer’s favor.

After transfer

Export the baseline, preserve backups and document the handover date. Move billing and administrative control, then remove former access and obsolete ownership-verification methods without interrupting services.

Re-run the search engine audit against the same revenue pages, conversion paths and prompt set. Check availability and transactions immediately, then schedule follow-up reviews, such as days 7, 30 and 60. Those are observation points, not promised recovery periods.

Avoid combining ownership transfer with an unnecessary redesign or domain change. If a migration is required, use a separate plan for monitoring search during a WordPress migration.

Accept fixes only after the original failure is resolved. A repaired canonical should point to the intended indexable URL; a repaired form should produce a valid lead; a visibility claim should withstand repeated comparable checks. Preserve both successful tests and remaining failures so the acquisition team can distinguish completed remediation from work still carrying financial risk.

Frequently asked questions

Can I audit a website without seller access? A public search engine audit can reveal technical issues, visible content and some search exposure. It cannot reliably verify earnings, private manual actions or ownership rights. Treat those as unresolved conditions, not clean findings.

Which audit tool should a buyer use first? Start with first-party search, analytics and revenue evidence. Add a crawler for technical coverage, performance testing for customer journeys and AI monitoring for answer visibility. Choose tools around missing evidence rather than a single headline score.

What findings justify walking away? Unverifiable earnings, material rights that cannot transfer and concealed dependencies can undermine the acquisition. The decision depends on severity, evidence and whether enforceable closing conditions resolve the problem.

Does a clean audit guarantee rankings will survive? No. Search results, competitors and AI answers change. A strong review reduces avoidable uncertainty and creates a baseline for detecting problems after ownership changes.

Start with a free AI visibility audit

Start with a free AI visibility audit from CapstonAI to establish how the target brand appears across AI search before committing to the acquisition. Pair that baseline with verified earnings, technical evidence and a documented handover. Buy the search asset you can substantiate, with unresolved risks explicitly reflected in the deal.

Share on
Summarise with

Related content