The 2026 Lighting Company SEO Verification Checklist

Lighting catalogs can become difficult to crawl and maintain when filters, images, and product retirement rules are not governed explicitly. Treat each check below as a small control with evidence, ownership, and a repeatable validation step.

Check: Faceted navigation and product filtering Evidence required: Crawl exports, index coverage, canonical behavior, parameter rules, and representative filtered URLs for attributes such as color temperature, output, wattage, finish, control type, or rating.

Pass condition: Important category and product pages remain crawlable and indexable while low-value filter combinations do not create uncontrolled duplicate or near-duplicate URL sets. Fail condition: Filter combinations generate large indexable URL families, canonicals conflict with intended pages, or users and crawlers cannot reach important catalog paths consistently.

Severity: High when indexation or crawl allocation is materially affected. Owner: Technical SEO and web engineering, with merchandising input on which filters represent meaningful catalog demand. Corrective action: Define which filtered states deserve stable pages, consolidate or control low-value combinations, and align canonical, internal-link, and parameter behavior with that decision.

Validation: Re-crawl representative catalog paths and confirm that intended pages resolve, canonicalize, and index consistently.

Check: Image delivery for product and lifestyle assets Evidence required: Representative product and collection pages, rendered image dimensions, transfer size, responsive source behavior, alternative text, and field performance where available.

Pass condition: Images remain visually useful while delivery is proportionate to display size, descriptive context is accurate, and large assets do not create avoidable performance problems. Fail condition: Oversized originals are served broadly, critical catalog pages become unnecessarily heavy, or image context is generic or misleading.

Severity: Medium to High depending on the affected templates. Owner: Web engineering for delivery and the content or design team for image meaning and asset quality. Corrective action: Use appropriate responsive delivery, compression, caching, and modern formats supported by the stack, while keeping image descriptions factual.

Validation: Re-test representative pages in production and compare measured loading behavior rather than assuming a format change alone solved the issue.

Check: Discontinued product handling Evidence required: A sample of retired SKUs, inbound-link data, replacement mappings, technical-file references, and current catalog status. Pass condition: Each retired product has an intentional outcome based on user need and catalog reality, such as a maintained archive page, a relevant replacement path, or another justified status.

Fail condition: Retired products disappear without explanation, redirect to unrelated destinations, or leave broken internal links and obsolete downloads. Severity: High for products with meaningful links, demand, or specification history.

Owner: Product management, SEO, and web engineering. Corrective action: Create a documented retirement policy and apply it consistently across pages, files, links, and replacements. Review the lighting SEO mistakes guide when diagnosing recurring catalog failures.

Validation: Crawl retired-product samples, verify destination relevance, and confirm that internal links and technical resources reflect the current catalog.

Product pages should make the information a professional buyer needs visible, consistent, and connected to the correct fixture. Mark each check as passed only when the live page and the authoritative product source agree.

Check: Structured product information Evidence required: Live product pages, visible technical fields, current product records, and the structured data actually rendered on representative templates. Pass condition: Structured data accurately reflects visible page content and uses supported properties that match the product information users can verify on the page.

Fail condition: Markup contains hidden, stale, unsupported, or conflicting claims, or product pages omit essential visible information while relying on markup to compensate. Severity: High when inaccurate markup or product data can misrepresent the fixture.

Owner: Product data, SEO, and web engineering. Corrective action: Align structured fields with the authoritative product source and visible page content. Do not add markup solely to chase a search feature.

Validation: Compare rendered markup with visible product information and test representative pages using the relevant validation tools.

Check: Crawlable IES and specification resources Evidence required: Product pages, IES files, specification PDFs, crawl paths, file naming, response status, and links from the canonical product page.

Pass condition: Professional resources that genuinely exist are reachable from the appropriate product page, use stable descriptive naming, and do not conflict with current product data. Fail condition: Files are orphaned, blocked unintentionally, attached to the wrong model, or discoverable only through outdated navigation.

Severity: High for specification-grade products. Owner: Product engineering or documentation for file accuracy, with the web team responsible for publishing and linking. Corrective action: Consolidate each product's technical resources around the canonical page and maintain clear file ownership and update procedures.

Validation: Crawl representative resources, open them from the live product page, and confirm that model identifiers and technical values match the current product record.

Check: Technical long-tail intent Evidence required: Search Console queries, internal search logs where available, sales and specification questions, and product attributes visible on the site. Pass condition: Product and application pages naturally answer relevant technical queries that match real capabilities, including use cases such as IP65 rated outdoor fixtures or Title 24 compliant products when those claims are accurate and applicable.

Fail condition: Pages target technical phrases the product cannot substantiate, or useful specification details exist internally but are absent from the page. Severity: Medium to High depending on commercial importance.

Owner: Product marketing with engineering or compliance review for technical accuracy. Corrective action: Add factual technical context, application guidance, and supporting resources to the pages that genuinely satisfy the query.

Validation: Review the live page against the authoritative product source and confirm that the query-to-page mapping is specific, accurate, and non-duplicative.

A showroom check should verify a real place and the information people need to visit, call, or evaluate it. Do not pass an item merely because a page exists.

Check: Google Business Profile and physical showroom accuracy Evidence required: The live business profile, showroom website page, signage or internal location records, opening hours, categories, contact information, and customer-facing services.

Pass condition: Profile information matches the real showroom and the linked website page gives useful local information for visitors and specifiers. Fail condition: Categories, hours, address details, services, or website information conflict with the real location, or a profile is maintained for a location that is not eligible or operational.

Severity: High for customer-facing showrooms. Owner: Local operations with marketing or SEO oversight. Corrective action: Correct factual discrepancies and keep the profile aligned with the showroom's actual operations.

Do not treat routine profile activity as a guaranteed ranking factor. Validation: Compare the live profile, website, and internal location record and verify that users can contact or visit the showroom using current information.

Check: Location-specific project and showroom content Evidence required: Real project records, showroom services, local portfolio assets, and the location page itself. Pass condition: The page contains useful information specific to the genuine location, such as services, access details, relevant projects, appointment information, or local product context.

Fail condition: The page is mostly duplicated from another location or exists only to target a place name without meaningful local information. Severity: Medium to High. Owner: Local marketing, showroom management, and the content team.

Corrective action: Replace boilerplate with verified local information and connect genuine project evidence to the relevant showroom or service context. Validation: Review the page with the local operator and confirm that each location-specific statement can be substantiated.

Check: Category H1 accuracy - High - 1 hour Evidence required: Priority category pages and their visible heading text. Pass condition: The heading describes the actual category and audience without forcing manufacturer or wholesale terminology where it does not apply.

Owner: SEO and merchandising. Corrective action: Rewrite inaccurate category headings and keep them aligned with the visible catalog. Validation: Re-crawl and inspect the rendered heading on representative templates.

Check: Product hero image compression - Medium - 2 hours Evidence required: Representative product templates, source assets, and measured transfer size. Pass condition: Hero images remain visually appropriate while avoiding unnecessary payload.

Owner: Design and web engineering. Corrective action: Apply consistent responsive image handling and compression rules. Validation: Compare production pages before and after deployment using measured page data.

Check: Internal links to the core strategy page - High - 2 hours Evidence required: Relevant editorial pages and the existing core lighting SEO page. Pass condition: Links appear only where they help users reach the broader strategy context and use descriptive anchor wording.

Owner: Content and SEO. Corrective action: Add or revise contextual links where they genuinely support the reader journey. Validation: Crawl the linking pages and confirm the destination, anchor, and context remain relevant.

• Compliance terminology without evidence: Terms such as Dark Sky or Title 24 should appear only when they accurately apply to the product, project, or guidance being discussed. Evidence required: current product or compliance documentation. Pass when the claim is specific and supportable; fail when copied broadly across unrelated pages. Severity: High when a technical claim can mislead a specifier. Owner: compliance or engineering. Corrective action: remove or qualify unsupported language. Validation: sample affected pages against current documentation.
• Duplicated manufacturer copy across showroom sites: Evidence required: representative product and category URLs from each site. Pass when each page has a justified purpose and useful differentiated information; fail when near-identical pages multiply without user value. Severity: Medium to High depending on scale. Owner: content, merchandising, and SEO. Corrective action: consolidate or differentiate pages based on actual audience and location needs. Validation: re-crawl and compare duplicate patterns.
• Question content created only to imitate search features: Evidence required: editorial briefs, query data, and the published page. Pass when questions answer real buyer or specifier needs; fail when content exists only to target a search-result feature. Severity: Medium. Owner: content strategy. Corrective action: rewrite around genuine decision questions and measurable user needs. Validation: confirm the page remains useful even if no enhanced search presentation appears.