The 2026 Evidence Checklist for IT Company and MSP SEO

Technical checks should answer a narrow question: can search systems and buyers reliably reach, render, understand, and use the pages that matter? Record the tested URL, the tool or browser evidence, the failure condition, and the owner before changing implementation. Avoid inferring health from design quality, hosting reputation, or a single aggregate score.

Page performance on representative templates Evidence required: PageSpeed Insights or GTmetrix output for the homepage, a core managed-service page, a representative industry page when one exists, and a contact or conversion path, plus field data when available.

Pass/fail: pass when no repeatable measured condition materially interferes with loading, reading, navigation, form use, or contact actions on the tested template; fail when the same meaningful problem can be reproduced on an important path.

Severity: high when the issue recurs across revenue-critical templates, medium when it affects a narrower path, and lower when it is isolated and noncritical. Owner: developer or site administrator. Corrective action: fix the measured cause rather than optimizing the score in isolation.

Typical causes may include unnecessary script execution, oversized media, unstable layout space, or delivery configuration. Validation: retest the same URLs under comparable conditions and compare field evidence when it exists. Estimated effort: 4-6 hours. Tools: Google PageSpeed Insights, GTmetrix.

Secure delivery and transport configuration Evidence required: browser security state, certificate details, redirect behavior, mixed-content inspection, and an SSL Labs or DigiCert configuration check.

Pass/fail: pass when important public pages load securely without certificate or mixed-content warnings and the configured security policy matches the site's operational requirements; fail when a buyer encounters a certificate, protocol, redirect, or resource-loading problem.

Severity: critical when an important public page cannot be used securely, otherwise based on the affected path and recurrence. Owner: developer, hosting administrator, or security owner. Corrective action: repair the specific certificate, redirect, protocol, or insecure-resource issue and document any configuration dependency.

Validation: repeat the browser and external configuration checks after deployment, using the same destinations that originally failed. Estimated effort: 1 hour. Tools: DigiCert, SSL Labs.

Service and LocalBusiness structured data Evidence required: the live machine-readable markup, the visible facts on the page, the business source of truth, and Google Rich Results Test output where the test is applicable.

Pass/fail: pass when markup is syntactically valid, describes the entity or service actually shown, and matches current visible facts; fail when markup is invalid, misleading, stale, or describes a location or offering that is not real.

Severity: medium for inaccurate descriptive markup and higher when the mismatch conflicts with core identity or service facts. Owner: developer or SEO owner with business review. Corrective action: remove unsupported properties, use an appropriate type, and align the markup with the page and current business records.

Validation: retest the published markup, compare it with the rendered page, and confirm the same facts remain visible to users. Structured data helps Google understand which IT services the page describes and can make the page eligible for rich results, though eligibility does not guarantee that they appear. Estimated effort: 2-3 hours. Tools: Schema.org, Google Rich Results Test.

Broken destinations and internal paths Evidence required: a crawler report, the referring pages that contain important links, and manual checks for high-value destinations, including the IT company service hub.

Pass/fail: fail when a required internal path resolves to a 404 response, enters a loop, reaches an unintended destination, or leaves a core buyer path unusable; pass when important links resolve to the intended live content.

Severity: high when the break blocks discovery, service evaluation, or contact flow, and medium for noncritical references. Owner: developer or content editor. Corrective action: restore the intended page, correct the link on the referring page, or use an appropriate redirect when content has genuinely moved.

Validation: recrawl the affected paths, click-test the repaired links, and confirm that the final destination is the one documented in the audit. Estimated effort: 2 hours. Tools: Screaming Frog, Ahrefs.

Content checks should determine whether a business buyer can identify what the MSP actually provides, who the service fits, what the operational boundaries are, what evidence supports the claims, and how to take the next step.

A page should not pass because it targets a keyword; it should pass because its claims are accurate, its scope is clear, and the responsible service owner can substantiate it.

Industry and vertical service pages Evidence required: current service documentation, the markets actually served, subject-matter approval, recurring sales or support questions, and the live page. Pass/fail: pass when the MSP genuinely serves the vertical and the page explains relevant service scope, buyer concerns, operational considerations, limitations, proof, and next actions; fail when the page is mainly a generic template with industry labels swapped in, implies unsupported expertise, or leaves the service relationship unclear.

Severity: high. Estimated effort: 10-15 hours. Owner: marketing owner with review from technical or service leadership. Corrective action: rewrite around real offerings, actual buyer questions, and substantiated constraints, or remove the page if the underlying service proposition is not real.

Validation: compare the final copy with current delivery documentation and obtain approval from the accountable subject-matter owner. Tools: SurferSEO, MarketMuse.

Technical explanations and glossary material Evidence required: query evidence, language used by prospects and account teams, support questions, and subject-matter review for terms such as SOC2 compliance.

Pass/fail: pass when the content answers a real evaluation question accurately and makes the term understandable in the context of the MSP's service; fail when it exists mainly to create search inventory, overstates what the MSP can support, or uses terminology the responsible technical reviewer cannot defend.

Severity: medium. Estimated effort: 8 hours. Owner: content owner with technical reviewer. Corrective action: revise the explanation around the buyer decision, distinguish the MSP's responsibility from the customer's responsibility where relevant, and connect the explanation to a service only when the relationship is real.

Validation: confirm factual accuracy, then review Search Console evidence after indexing to determine whether the page is reaching the intended query set rather than unrelated informational demand. Tools: Semrush, AnswerThePublic.

Case studies and proof pages Evidence required: Internal Project Data, Client Interviews, permission for identifiable details where required, the original measurement record, and delivery-team review.

Pass/fail: pass when the page distinguishes the starting condition, work performed, scope boundaries, evidence source, and verifiable result; fail when it uses vague success language, invented outcomes, unsupported attribution, or claims that cannot be traced to a record.

Severity: high. Estimated effort: 5 hours per case study. Owner: marketing owner with delivery and client-approval input where needed. Corrective action: remove or narrow unsupported statements, document the available evidence, and state material limitations instead of filling gaps with promotional language.

Validation: recheck every factual statement against the original project record and repeat that review when the case study is materially updated. Google describes E-E-A-T as qualities its systems look for in helpful content rather than a numeric score, and real-world examples of resolving downtime or preventing data breaches are how an MSP demonstrates that expertise to buyers.

Local checks should verify whether the business information presented to buyers is genuine, consistent, useful, and operationally current. Do not create pages, profiles, or claims for nominal markets that lack real location-specific substance, and do not treat any profile activity as a guaranteed ranking factor.

Google Business Profile accuracy Evidence required: the live profile, current business records, website contact information, and the categories currently available in the profile interface. Pass/fail: pass when identity, contact details, website destination, hours, and applicable location or service-area information match operational reality; fail when a material field conflicts with the source of truth or the profile represents an ineligible or nonexistent location.

Severity: critical for wrong identity or contact information, high for a material location mismatch, and medium for incomplete descriptive fields that do not misrepresent the business. Owner: verified profile manager with operations review.

Corrective action: update the inaccurate field, retain the business record used as evidence, and avoid adding unsupported geographic detail simply for search visibility. Validation: confirm the accepted edit is live and still agrees with the website and business record.

Set the primary category to Managed Service Provider or Computer Support Specialist to match local intent, after confirming which of these labels is currently available in the profile interface. Estimated effort: 2 hours. Tools: Google Business Profile Manager.

Genuine location pages Evidence required: proof that the location is real, current operational information, location-specific service details, and a clear buyer reason for the page to exist. Pass/fail: pass when each location page represents a genuine place and contains substantive facts that would help a buyer evaluate service there; fail when pages are created by changing city names, imply a presence that does not exist, or repeat generic content without useful local substance.

Severity: high for misleading representation and medium for thin but accurate pages. Owner: marketing owner with operations review. Corrective action: consolidate unsupported pages, remove misleading claims, and strengthen legitimate pages with accurate local team, service, contact, or operating information.

Validation: compare the published page with current business records and manually verify that internal links lead to the correct location content. Estimated effort: 5-10 hours. Tools: BrightLocal, Whitespark.

Customer review process Evidence required: the live review profile, recent request examples, the written eligibility rule, and the process used by customer-facing teams. Pass/fail: pass when eligible customers are asked consistently for honest feedback without incentives, review gating, discouraging negative feedback, or selecting only customers expected to be satisfied; fail when the request process filters by predicted sentiment or pressures customers toward a 5-star outcome.

Severity: high for manipulative solicitation and medium for inconsistent handling that creates avoidable bias. Owner: customer success, account management, or the designated reputation owner. Corrective action: replace selective outreach with a consistent neutral request, document who is eligible, and train the team to apply the same rule regardless of expected sentiment.

Validation: audit a recent set of requests and confirm the rule was applied consistently. Reviews matter to buyer evaluation in a high-trust service like IT support, and review count and rating also feed the prominence Google uses to rank local results, although no review volume, recency, or response activity guarantees a ranking. Estimated effort: ongoing. Tools: Grade.us, BirdEye.

Service-page title tags - Priority: High - estimated effort: 1 hour. Evidence required: an export of current titles mapped to the live service URLs and the primary purpose of each page. Pass/fail: fail when an important service page has a duplicate, placeholder, misleading, or materially unclear title; pass when the title accurately identifies the service page and distinguishes it from adjacent pages.

Severity: high when unclear or duplicate titles affect core commercial pages. Owner: SEO or content editor. Corrective action: rewrite only the affected titles around the actual service and page purpose without adding unsupported claims. Validation: recrawl the site and compare the published tags with the approved mapping.

Relevant industry directory records, including Clutch, G2, and UpCity - Priority: Medium - estimated effort: 3 hours. Evidence required: current public records and the business source of truth for identity, contact, and service information.

Pass/fail: pass when a legitimate record accurately reflects the company; fail when a live record contains a material factual mismatch. Severity: medium unless the mismatch creates a significant identity or contact problem.

Owner: marketing operations. Corrective action: correct factual inconsistencies and remove unsupported descriptions without treating directory presence itself as a guaranteed ranking lever. Validation: revisit the public record after the edit is accepted and compare it with the source of truth.

Duplicate content on genuine location pages - Priority: High - estimated effort: 2 hours. Evidence required: a side-by-side comparison of live location pages plus records proving each represented location is genuine.

Pass/fail: fail when pages differ mainly by place name, repeat generic service claims, or make unsupported local statements; pass when each page contains accurate location-specific information that serves a distinct buyer need.

Severity: high when duplication accompanies misleading location representation, otherwise based on the commercial importance of the pages. Owner: content owner with operations review. Corrective action: consolidate unsupported pages or rewrite legitimate pages around real local facts, service differences, team information, and contact details where those facts exist.

Validation: compare the final pages side by side, verify each against business records, and recrawl the internal links that point to them.

• Failing to support near-me queries with local evidence. 'Near me' queries are dominant in the IT support space, so the site has to answer them with real location facts. Evidence required: Search Console query data, a review of the actual local results, and genuine location or service-area facts. Pass/fail: fail when the site gives buyers no accurate location or service-area information for those queries, when copy inserts 'near me' language mechanically, or when it implies proximity that the business cannot substantiate; pass when local wording reflects real service coverage and helps the reader make a geographic decision. Owner: local SEO or content owner with operations review. Corrective action: replace manufactured proximity language with accurate location, service-area, and contact information. Validation: reread the page against the business source of truth and monitor the intended query set without treating phrasing as a guaranteed ranking mechanism.
• Using generic imagery as if it were operational proof. Evidence required: the image source, usage context, and the claim a reader could reasonably infer from the placement. Pass/fail: fail when a stock image is presented in a way that suggests it depicts the actual team, office, infrastructure, client work, or delivery process; pass when illustrative imagery is used transparently and does not carry a factual claim it cannot support. Owner: marketing or brand owner. Corrective action: replace the image with real permissioned proof where appropriate or change the context so the illustration is not treated as evidence. Validation: confirm the final page clearly distinguishes demonstrable proof from generic visuals and uses E-E-A-T only as a credibility lens.
• Optimizing core pages around internal jargon instead of buyer language. Evidence required: query data, sales and account-team language, support conversations, and a content review against the IT company SEO mistakes guide. Pass/fail: fail when important pages rely on internal terminology that obscures the service, problem, responsibility, or next step; pass when the language remains technically accurate while being understandable to the intended decision-maker. Owner: content owner with subject-matter review. Corrective action: replace unnecessary internal shorthand with buyer language, define terms that are genuinely necessary, and preserve technical accuracy. Validation: reread the page against the target query evidence and the language used in real sales conversations, then confirm that the service proposition remains precise.