Verify the SEO work that helps prospective interior design clients find and evaluate your studio

This guide is for residential and commercial interior design studios, kitchen and bath specialists, staging teams, and other design practices that need a repeatable way to inspect search visibility. Use the interior design SEO audit guide when you need a broader diagnostic, then use this page to turn findings into assignable checks.

You do not need to be a developer to run the checklist. Each task states the evidence to collect, the pass or fail condition, severity, owner, corrective action, and a validation step. Owners are written as Studio, SEO, Developer, or a shared combination so responsibilities are explicit.

Before the tiered work, add these two preflight checks so the full program has a clear baseline:

• Search ownership baseline. Evidence required: current access to the website CMS, Google Business Profile, analytics, and Search Console. Pass: the studio can identify who controls each account and can export or inspect current settings. Fail: access is missing, duplicated, or controlled by an unknown party. Severity: high. Owner: Studio. Corrective action: recover or document access without changing public data unnecessarily. Validation: sign in to each system and record the accountable owner.
• Business information baseline. Evidence required: the studio's current legal or public-facing name, contact details, genuine locations, core services, and hours where applicable. Pass: the same approved information is available to the people editing the site and profile. Fail: teams are using conflicting versions. Severity: high. Owner: Studio. Corrective action: establish one approved source of truth. Validation: compare the approved details against the homepage, contact page, and profile before making SEO changes.

Use the rest of the checklist as an evidence log, not a box-ticking exercise. A task passes only when its stated condition can be verified.

All 45 checks use the same decision pattern: gather evidence, test the pass condition, record severity, assign an owner, correct the failure, and validate again. This keeps implementation decisions separate from assumptions about rankings.

Tier 1: foundation. Treat these as the first operational controls because they affect whether search systems and prospective clients can accurately identify the business, its services, and its pages. Complete them before expanding lower-priority work.

Tier 2: growth. Start after the foundation is stable. Use these checks to improve service coverage, project evidence, usability, reviews, and content quality without creating thin pages or unsupported claims.

For previously completed foundation changes, use a 4-8 week observation window as a practical comparison period while recognizing that search visibility can change for many reasons and no timing is guaranteed.

Return to Tier 1 before adding Tier 2 work if core information becomes inconsistent. A Tier 1 failure should not be hidden by more publishing. For scheduling, the original sequence can still be read as Tier 1 first, then a review during weeks 3-12, followed by Tier 3 maintenance. Tier 3 supports durability; it does not replace Tier 1.

The related interior design SEO cost guide can help with make-or-buy decisions after you identify which failed checks require outside help.

Google Business Profile - 4 checks

• Profile ownership and status. Evidence required: the live profile and current manager access. Pass: the correct business controls the profile and the displayed status matches the business. Fail: ownership is unclear, access is missing, or a duplicate is being treated as the primary profile. Severity: critical. Owner: Studio. Corrective action: recover legitimate access and follow Google's supported duplicate or ownership processes rather than attempting to redirect another business's profile. Validation: confirm the intended profile is accessible and displays the approved business identity.
• Core profile information. Evidence required: profile name, category, address or service-area configuration where eligible, phone, website, and hours. Pass: fields are complete, accurate, and consistent with the studio's approved information. Fail: data is outdated, embellished, or inconsistent. Severity: critical. Owner: Studio. Corrective action: correct factual fields only. Validation: compare the live profile with the approved source of truth.
• Project imagery. Evidence required: a representative set of 10-15 original project or studio images that the firm has the right to publish. Pass: images are relevant, current enough to represent the practice, and not stock substitutes presented as client work. Fail: the profile relies on irrelevant, misleading, or unusable imagery. Severity: high. Owner: Studio. Corrective action: replace weak assets with rights-cleared project imagery. Validation: review the public gallery and confirm each image accurately represents the business.
• Profile features. Evidence required: the currently available profile controls and contact paths. Pass: useful supported features are configured accurately and monitored when the studio chooses to use them. Fail: enabled features point to unattended or incorrect destinations. Severity: moderate. Owner: Studio. Corrective action: configure only features the team can maintain. Validation: test the public contact path and confirm it reaches the intended destination.

On-page essentials - 6 checks

• Title tags. Evidence required: rendered title tags for the homepage, service pages, project pages, and location pages that genuinely exist. Pass: each important page has a concise, distinct title that describes its page intent and, where useful, location. Fail: titles are missing, duplicated, misleading, or stuffed with repeated terms. Severity: critical. Owner: SEO. Corrective action: rewrite titles around the actual page purpose and business name. Validation: crawl the site and compare page titles for uniqueness and intent.
• Meta descriptions. Evidence required: current descriptions in source or CMS. Pass: important pages have unique, accurate descriptions that summarize the page without unsupported promises; a 150-160 character range can be used as an editing reference, not a display guarantee. Fail: descriptions are absent, duplicated, deceptive, or unusably repetitive. Severity: moderate. Owner: SEO. Corrective action: rewrite the weak descriptions. Validation: inspect page source or crawl output after publishing.
• Primary heading. Evidence required: the rendered H1 and surrounding page copy. Pass: each main page presents one clear primary topic to readers without using heading text as a keyword list. Fail: the page lacks a meaningful primary heading or uses conflicting primary topics. Severity: high. Owner: SEO. Corrective action: align the main heading with the page's actual service, project, or location intent. Validation: review the rendered page on desktop and mobile.
• Image alternative text. Evidence required: alt attributes for meaningful images and empty alternatives for decorative images where appropriate. Pass: alternatives describe the useful visual information without forcing locations or keywords. Fail: text is missing where needed, repeats filenames, or is stuffed with marketing terms. Severity: high. Owner: Studio plus SEO. Corrective action: write concise, context-aware alternatives. Validation: inspect representative pages with images disabled or through accessibility tooling.
• Structured data accuracy. Evidence required: rendered structured data and the visible facts it describes. Pass: markup uses supported vocabulary, matches visible content, and does not claim reviews, locations, or services that are not present. Fail: markup is invalid, misleading, or disconnected from the page. Severity: high. Owner: SEO plus Developer. Corrective action: remove unsupported properties and repair syntax. Validation: test the rendered markup with Google's available validation tools and inspect the page source. Structured data can help systems understand content or qualify pages for supported features, but it is not a guaranteed ranking factor.
• Service-page usefulness. Evidence required: the full copy, project examples, process details, and calls to action on each core service page. Pass: each page provides enough distinct information to help a prospective client understand the service; 400 words can be used as a review prompt, not a minimum enforced by Google. Fail: pages are thin duplicates or exist only to target a phrase. Severity: critical. Owner: Studio plus SEO. Corrective action: merge redundant pages or expand them with genuine service-specific information. Validation: compare service pages side by side and confirm each serves a distinct reader need.

Site structure - 3 checks

• Navigation depth. Evidence required: a crawl and the site's main navigation. Pass: important service and project pages can be reached through logical paths, with no more than 3 clicks used as an internal usability target rather than a search rule. Fail: key pages are orphaned or buried behind confusing paths. Severity: high. Owner: SEO plus Developer. Corrective action: simplify navigation and add relevant contextual links. Validation: start at the homepage and manually reach each priority page.
• Breadcrumbs. Evidence required: rendered breadcrumb links and any related markup. Pass: breadcrumbs reflect the site's actual hierarchy, are usable to visitors, and use valid markup if implemented. Fail: trails are missing where hierarchy is hard to understand, point to incorrect parents, or use invalid markup. Severity: moderate. Owner: Developer plus SEO. Corrective action: implement or repair visible breadcrumb navigation. Validation: click each breadcrumb path and test its markup if present.
• Internal links. Evidence required: crawl data and a sample of service and project pages. Pass: links connect related services, relevant project examples, and useful supporting content with descriptive anchors. Fail: important pages receive no internal links or links are inserted only to repeat keywords. Severity: high. Owner: SEO. Corrective action: add contextually useful links where readers would benefit. Validation: recrawl and confirm priority pages are discoverable through relevant internal paths.

Content and search demand - 8 checks

• Search-term set. Evidence required: Search Console data, keyword-tool exports if available, and a list of real client questions. Pass: the working set includes 20-30 service and local-intent terms mapped to existing or planned pages without treating volume estimates as guarantees. Fail: terms are chosen only for apparent volume or duplicate the same intent across many pages. Severity: high. Owner: SEO. Corrective action: group terms by reader intent and map each group to the best page. Validation: review the map for overlap and confirm every proposed page has a distinct purpose.
• Publishing plan. Evidence required: a calendar tied to business questions, project evidence, and available subject-matter input. Pass: the team can realistically publish 1-2 useful pieces during the chosen planning period without sacrificing page quality. Fail: the schedule exists only to hit a cadence or produces repetitive posts. Severity: moderate. Owner: Studio plus SEO. Corrective action: reduce frequency and prioritize useful topics. Validation: compare each planned piece with an identified reader question and a source of firsthand studio information.
• Service questions. Evidence required: inquiry emails, sales-call notes, consultation questions, or other first-party records. Pass: pages answer genuine questions about scope, fit, process, and decision criteria. Fail: FAQ copy is generic, duplicated, or created mainly to target long-tail phrases. Severity: moderate. Owner: Studio plus SEO. Corrective action: replace generic questions with recurring client questions and accurate answers. Validation: confirm the answers remain consistent with the related service page.
• Project case studies. Evidence required: approved project facts, images, scope, constraints, and outcomes the studio can substantiate. Pass: each case study explains what was done and why without inventing client claims. Fail: the page is only a gallery or contains unsupported performance language. Severity: high. Owner: Studio plus SEO. Corrective action: add factual project context and remove claims that cannot be supported. Validation: compare published copy against approved project records.
• Existing-page alignment. Evidence required: target-page copy and its search-demand map. Pass: introductions, H2 and H3 subheadings, body copy, and internal links support the page's actual intent naturally. Fail: headings repeat keywords without helping readers or the page addresses conflicting intents. Severity: high. Owner: SEO. Corrective action: rewrite the structure around the reader's decision path. Validation: reread the page without the keyword list and confirm it still makes sense.
• Location-page eligibility. Evidence required: proof of a genuine office or service presence plus useful location-specific information such as projects, process differences, access details, or market-relevant examples. Pass: a dedicated page is justified by distinct local information. Fail: a page exists only to swap a city name. Severity: high. Owner: Studio plus SEO. Corrective action: merge thin pages into a broader service page or build a genuinely useful location page; 400 words can be a review prompt, not a rule. Validation: compare location pages and confirm the information is materially different and accurate.
• Downloadable resources. Evidence required: the resource, landing copy, form behavior, privacy wording, and delivery path. Pass: the asset helps a prospective client make a design decision and the form accurately explains what happens after submission. Fail: the asset is thin, inaccessible, or collects data without clear context. Severity: moderate. Owner: Studio plus Marketing. Corrective action: improve the resource or remove the gate. Validation: complete the form as a visitor and inspect the delivered asset.
• Structured-data scope. Evidence required: markup on service, breadcrumb, review, or question content where supported and accurate. Pass: implemented types match visible content and current documentation. Fail: markup is added merely to seek a special result or includes unsupported properties. Severity: moderate. Owner: SEO plus Developer. Corrective action: keep only accurate, supported markup. Validation: test rendered code and compare every property with visible page content. Question content can be useful to readers, but do not rely on FAQPage markup for a Google FAQ rich result.

User experience and speed - 4 checks

• Mobile layout. Evidence required: real-device checks across representative phones and tablets. Pass: navigation, forms, project galleries, text, and calls to action remain usable without accidental taps or clipped content. Fail: essential interactions break or important content is inaccessible. Severity: critical. Owner: Developer. Corrective action: repair responsive layout and interaction issues. Validation: repeat the same tasks on real devices after deployment.
• Image delivery. Evidence required: file sizes, dimensions, formats, and rendered quality. Pass: images are appropriately sized for their display context and preserve acceptable visual quality. Fail: oversized assets cause avoidable transfer or visibly degraded images reduce portfolio usefulness. Severity: high. Owner: Developer plus Studio. Corrective action: resize, compress, and use suitable modern formats where supported. Validation: compare transfer size and rendered quality before and after.
• Core Web Vitals review. Evidence required: field data where available and diagnostic lab data. Pass: the team can identify which templates or assets cause poor experiences and has documented remediation for confirmed issues. Fail: lab scores are treated as a ranking guarantee or red flags are ignored without investigation. Severity: high. Owner: Developer plus SEO. Corrective action: fix confirmed bottlenecks such as slow hero assets, layout shifts, or heavy script work. Validation: rerun diagnostics and review subsequent field data when enough data exists.
• Deferred media. Evidence required: page source, network behavior, and visual checks for below-the-fold media. Pass: noncritical images or videos can be deferred without hiding important above-the-fold content or breaking galleries. Fail: everything loads eagerly or deferral creates missing content. Severity: moderate. Owner: Developer. Corrective action: configure safe lazy loading. Validation: inspect network requests and scroll through the page after a clean load.

Reviews and reputation - 3 checks

• Review request process. Evidence required: the message sent to eligible customers and the destination link. Pass: requests ask eligible customers consistently for honest feedback without incentives, discouraging negative feedback, or selecting only satisfied customers. Fail: the process gates, pressures, or selectively solicits. Severity: critical. Owner: Studio. Corrective action: replace selective scripts with a neutral process. Validation: audit recent request messages and confirm the same eligibility rule is applied consistently.
• Review response workflow. Evidence required: recent public reviews and internal assignment rules. Pass: the studio has a practical workflow for respectful, privacy-conscious responses; 48 hours may be used as an internal service target, not a documented Google ranking factor. Fail: responses expose private details, become argumentative, or have no owner. Severity: moderate. Owner: Studio. Corrective action: use a factual response process and escalate sensitive cases. Validation: sample recent responses for tone, privacy, and accuracy.
• Reputation monitoring. Evidence required: a recurring check of public review platforms that matter to the business. Pass: the team notices new feedback, records themes, and corrects factual profile issues when found. Fail: monitoring is absent or review volume is treated as a guaranteed ranking lever. Severity: moderate. Owner: Studio. Corrective action: establish a sustainable monitoring routine. Validation: document the last review check and any action taken.

Technical SEO - 6 checks

• Sitemap discovery. Evidence required: the current XML sitemap and submission status in supported webmaster tools. Pass: the sitemap resolves, lists canonical indexable pages, and is submitted where the studio chooses to use those tools. Fail: it is missing, stale, blocked, or filled with noncanonical URLs. Severity: high. Owner: Developer plus SEO. Corrective action: regenerate the sitemap from the intended canonical set. Validation: fetch it directly and compare listed URLs with a crawl.
• Indexing diagnostics. Evidence required: Search Console indexing reports, URL inspection for priority pages, robots directives, and server responses. Pass: intentional service and project pages are crawlable and eligible for indexing unless deliberately excluded. Fail: important pages are blocked, noindexed, redirected incorrectly, or return errors. Severity: critical. Owner: SEO plus Developer. Corrective action: repair the specific directive, response, or linking issue. Validation: reinspect representative URLs after deployment.
• Canonical signals. Evidence required: canonical tags, redirects, and internally linked URL versions. Pass: signals consistently identify the preferred page version and do not point unrelated pages at one destination. Fail: canonicals conflict with redirects or reference irrelevant pages. Severity: high. Owner: Developer plus SEO. Corrective action: align canonical tags, redirects, and internal links. Validation: crawl the site and inspect the canonical map.
• HTTPS consistency. Evidence required: certificate status, redirect behavior, and mixed-content checks. Pass: public pages load securely and insecure variants resolve appropriately. Fail: browsers warn about insecure resources or alternate protocol versions remain independently accessible. Severity: critical. Owner: Developer. Corrective action: repair certificate, redirect, or mixed-content issues. Validation: test representative URLs in a clean browser session and crawl for insecure resources.
• Duplicate URL control. Evidence required: crawl results for host variants, slash patterns, parameters, and duplicate page content. Pass: the site has a consistent preferred URL pattern and duplicates are consolidated appropriately. Fail: multiple indexable URLs expose substantially the same page without a clear preferred version. Severity: high. Owner: Developer plus SEO. Corrective action: use redirects, canonicals, internal-link cleanup, or parameter controls as appropriate. Validation: recrawl and confirm duplicate clusters are reduced to the intended versions.
• Broken links and redirect chains. Evidence required: a site crawl and server response map. Pass: important internal links resolve directly to the intended live destination. Fail: links return errors, lead through avoidable chains, or point to removed project pages without a relevant replacement. Severity: moderate. Owner: Developer plus SEO. Corrective action: update source links or create a relevant redirect where justified. Validation: recrawl after changes.

Analytics and measurement - 5 checks

• Google Analytics 4 configuration. Evidence required: property access, live data, filters or settings, and the site's deployed Google Analytics 4 tag. Pass: the property receives expected first-party site activity and the team can distinguish internal testing where configured. Fail: tracking is absent, duplicated, or firing on the wrong property. Severity: high. Owner: Analytics plus Developer. Corrective action: repair deployment and configuration. Validation: test a clean visit and confirm expected events in real-time or debug views.
• Inquiry events. Evidence required: form submission, phone-click, email-click, and other meaningful contact paths. Pass: the analytics setup records relevant inquiry actions without counting unrelated interactions as leads. Fail: events are missing, duplicated, or mislabeled. Severity: high. Owner: Analytics plus Developer. Corrective action: define and implement only meaningful events. Validation: trigger each action once in a test session and confirm the recorded event.
• Source analysis. Evidence required: acquisition reports and documented channel definitions. Pass: the team can compare organic search with other sources while recognizing attribution limitations. Fail: a single report is treated as complete proof of causation. Severity: moderate. Owner: SEO plus Analytics. Corrective action: document attribution limits and use consistent reporting views. Validation: compare reported sessions and inquiries across the agreed view.
• Reporting set. Evidence required: a recurring report covering visibility, search queries, landing pages, inquiry events, and business-relevant outcomes the studio can actually measure. Pass: each metric has a definition and owner. Fail: reports mix incompatible metrics or present keyword estimates as guaranteed results. Severity: moderate. Owner: SEO plus Studio. Corrective action: remove vanity metrics and document definitions. Validation: trace each reported number to its source report.
• Decision review. Evidence required: recent reporting, page-level changes, and notes on what was altered. Pass: the team can connect decisions to observed evidence without claiming that one change caused every movement. Fail: pages are rewritten or removed solely because of short-term noise. Severity: moderate. Owner: Studio plus SEO. Corrective action: use a documented hypothesis and validation plan before major changes. Validation: record the decision, supporting evidence, and next review point.

Ongoing maintenance - 4 checks

• Profile accuracy review. Evidence required: live Google Business Profile fields and recent approved project assets. Pass: information remains accurate and any new media is relevant and rights-cleared. Fail: the team posts merely to satisfy a cadence or leaves stale facts live. Severity: high. Owner: Studio. Corrective action: correct stale data and publish only useful updates. Validation: compare the profile with the approved business source of truth.
• Content refresh review. Evidence required: aging service, project, and informational pages plus updated studio facts. Pass: changes improve accuracy or usefulness. Fail: dates are changed without substantive updates or old claims remain unsupported. Severity: moderate. Owner: Studio plus SEO. Corrective action: update only what has materially changed and remove stale statements. Validation: compare revision history with the published page.
• Competitive observation. Evidence required: public search results and optional third-party research tools. Pass: observations are used to identify topics, formats, or gaps worth investigating without copying claims or treating tool estimates as facts. Fail: the team chases every competitor movement or imports unsupported metrics. Severity: low. Owner: SEO. Corrective action: keep a short evidence log and investigate only changes relevant to the studio's services. Validation: document the specific decision supported by each observation.
• Maintenance rhythm. Evidence required: a recurring task list with named owners. Pass: technical checks, profile accuracy, review monitoring, content updates, and measurement each have a sustainable cadence based on risk and business capacity. Fail: activity is performed only to appear active or because of an undocumented ranking theory. Severity: moderate. Owner: Studio plus SEO. Corrective action: set a realistic operating calendar. Validation: review completed tasks against the documented cadence and outcomes observed.

Use the downloadable matrix as the working copy for this guide. Each row should contain the evidence required, pass or fail condition, severity, owner, corrective action, and validation result. Add implementation scheduling separately so a due date never substitutes for proof that a task passed.

The source planning windows remain Stage 1-2 for foundation work and Stage 3-4 for the next implementation block. Treat those labels as project-management stages, not promises about search response.

The full 45-point program includes the preflight baseline plus the tiered checks above. Mark a row complete only after validation, and reopen it whenever business information, site templates, service offerings, or tracking changes.

For handoff decisions, the responsibility matrix should make the boundary clear: Studio owns factual business information and approved project evidence; SEO owns search intent, content mapping, and inspection; Developer owns code and template corrections; shared rows require both. The related interior design SEO statistics guide can be used to review previously published benchmarks carefully without treating an unsourced benchmark as verified proof.

The earlier timing labels can still organize capacity: Tier 1 is a focused 2-3 stage foundation, Tier 2 can occupy a broader 6-8 stage growth block, and Tier 3 is an ongoing maintenance stream. These are distinct implementation stages, not guaranteed ranking timelines.

If a failed row is outside your access or skill set, use the evidence already collected to brief the appropriate specialist. A useful handoff names the failed condition, shows the current evidence, states the corrective action, and defines how the fix will be validated.