The AI Queries Lighting Shoppers Ask
Someone asked Google's AI Overview "what size pendant light for a 6 foot kitchen island" last week, and the cited answer came from a competitor's sizing chart, not from the store that stocks the right pendant. Not because the store lacked the right size. Because nobody had published a chart matching island length to fixture diameter.
Most lighting stores publish a mood board and a wattage number and call it done. That is not enough, because a shopper measuring their kitchen island wants a specific answer, and AI retrieves the page that gives one. Lighting fixture stores earn AI citations by publishing room-size-to-fixture-size charts, bulb-base compatibility tables, and color-temperature guides with real Kelvin ranges. A store with twenty pages covering pendant sizing, bulb compatibility, and Kelvin selection for every room type gets cited over a store with two hundred product listings and no supporting content behind them.
Lighting shoppers do not browse a catalog first. They measure their room, note their ceiling height, and ask a question. Before buying a fixture, they ask AI in five predictable formats: sizing questions ("what size pendant light for a 6 foot kitchen island", "how big should a dining room chandelier be for a 10 by 12 room"), bulb compatibility questions ("what bulb base does this fixture use", "can I put an LED bulb in an old chandelier"), color temperature questions ("what Kelvin is best for a kitchen", "warm white vs daylight for a bathroom"), dimmer questions ("will this pendant work with a dimmer switch", "why does my LED chandelier flicker on a dimmer"), and style-fit questions ("what style pendant goes over a farmhouse table", "modern vs traditional chandelier for a foyer").
These query patterns, sizing, bulb compatibility, Kelvin, and dimmer pairing, are almost always answered with a synthesized AI response rather than a page of blue links, because each one has a concrete, checkable answer that AI is built to retrieve and state plainly. When someone types "what size chandelier for a 200 square foot dining room" into ChatGPT or Perplexity, they get a synthesized number pulled from whichever source states the sizing formula clearly. The store whose chart gets cited in that answer captures the shopper at the exact moment they are deciding what to buy. The question is whether your store is the source behind that answer or invisible to it entirely.
Start by pulling the question-format queries in your fixture category from your own search and support data. Filter for queries that start with "what size," "what bulb," "what Kelvin," and "will this work with." These are the patterns AI answers most confidently, because each one resolves to a specific fact rather than a matter of taste.
Content That Gets Lighting Fixture Stores Cited
Four content types earn lighting citations consistently. Room-size-to-fixture-size charts. Not "choose a size that fits your space." Instead: for a dining room chandelier, add the room's length and width in feet to get the approximate fixture diameter in inches (a 12 by 14 foot room points to roughly a 26 inch chandelier), and hang the bottom of the fixture 30 to 34 inches above the tabletop for a standard 8 foot ceiling, adding about 3 inches of extra drop for every foot of ceiling height beyond that. A page with this formula, plus a table showing common room dimensions mapped to fixture sizes, becomes the page AI retrieves whenever someone asks a sizing question in that room type.
Bulb-base and wattage compatibility tables. Every fixture page should state its exact base (E26 medium, E12 candelabra, E17 intermediate, GU10, GU24, MR16 bi-pin, or G9) next to maximum wattage and whether it accepts LED, halogen, or both. A comparison table showing "E26 vs E12: which fixtures use each base and why" answered with real specifications, not vague reassurance, is exactly the content AI cites when someone asks "can I use an LED bulb in this chandelier." The same specificity applies to wattage equivalence: a shopper replacing an old incandescent bulb needs to know that a 60 watt incandescent is roughly equivalent to an 8 to 9 watt LED, and a 100 watt incandescent to a 14 to 17 watt LED, because most fixtures list a maximum wattage rating that was written with incandescent bulbs in mind and a shopper trying to match brightness with a modern LED needs the conversion spelled out, not left as an exercise.
Color-temperature use-case guides with real Kelvin ranges. "What Kelvin is best for a kitchen" answered with a range: 2700K to 3000K for a cozy, warm-toned kitchen, 3500K to 4000K for a bright task-lit kitchen, and notes on how the two feel different under the same bulb wattage. Specificity is what earns the citation. A guide that lists actual Kelvin numbers by room type outperforms generic advice like "pick a temperature that suits your style" every time.
Dimmer compatibility content. "Why does my LED chandelier flicker on a dimmer" is one of the most common lighting support questions, and it has a real technical answer rooted in dimmer type. Covering it properly, and the schema that supports it, is where E-E-A-T becomes the differentiator. For the full method on keeping this kind of technical content accurate as products and bulb standards change, see our content refresh strategy guide.
The Expertise Problem (and How to Solve It)
Lighting content faces a specific trust problem: it sits at the intersection of interior design (subjective, style-driven) and electrical fact (objective, checkable). AI systems can tell the difference. A page that only talks about aesthetics ("this fixture adds warmth and character") earns no citation for a sizing or wiring question. A page that states verifiable electrical facts alongside design guidance earns citation for both.
Named author with real fixture or electrical experience. Not "written by our team." A specific person whose bio explains hands-on experience with fixture installation, sourcing, or lighting design. Person schema with jobTitle, a bio describing that experience, and sameAs links to a professional profile. AI retrieval systems weight author signals more heavily on content that includes electrical specifications, because getting a wattage or base wrong has a real consequence for the reader.
Verifiable, checkable claims. Every wattage, Kelvin range, and dimension in your content should be something a reader could independently confirm, from a bulb package, a fixture spec sheet, or a tape measure. Avoid vague claims like "our fixtures use quality materials." State the actual dimensions, the actual base type, the actual maximum wattage. AI systems increasingly cross-reference claims against a page's own schema markup, so consistency between your prose and your structured data strengthens citation confidence.
Real installation and fit guidance, not manufacturer boilerplate. A junction box height note, a ceiling weight-rating note for a heavy chandelier, or a plainly stated warning that a fixture needs a professional electrician for anything beyond a simple swap. This is the kind of grounded, specific detail that separates a store with genuine fixture expertise from a store repackaging manufacturer copy. It is what carries an E-E-A-T signal from a claim on paper to a claim AI is willing to cite.
Schema for Lighting Citations
Lighting fixture stores need schema that captures both the commerce layer and the technical specification layer, because shoppers and AI systems both need the bulb base, wattage, and dimensions before they need a price.
Product schema with fixture-specific properties. Beyond standard Product markup, include: bulb base type, maximum wattage per socket, number of sockets, fixture dimensions (width, height, and hanging chain or rod length), finish, and dimmer compatibility. If your content says "this pendant takes an E26 bulb up to 60 watts" and your Product schema confirms it, that consistency is a real signal AI systems can verify.
Article schema with a credentialed author. Every sizing guide, bulb-compatibility table, and Kelvin guide needs Article schema with a Person author whose jobTitle reflects real fixture or lighting-design experience. This is the difference between a page being treated as a source and a page being treated as marketing copy.
FAQPage for sizing and compatibility questions. The highest-value lighting queries are sizing and bulb questions. FAQPage schema surfaces these answers directly and signals to AI retrieval systems that your page authoritatively answers a specific question. Keep every FAQ answer as specific as the main content: exact inches, exact Kelvin, exact base type.
HowTo for sizing and installation content. A guide titled "how to choose the right size pendant light for your kitchen island" is a textbook HowTo schema candidate: measure the island, choose single or multiple fixtures, apply the sizing ratio, set the hanging height. Structured steps with real measurements at each one. Our broader AI search bible covers how these schema types interact with the four major AI surfaces.
Building Lighting Topic Clusters
Lighting content clusters work on three axes: by room type (kitchen, dining room, bedroom, bathroom, entryway, living room), by fixture type (pendant, chandelier, sconce, flush mount, table lamp, floor lamp), and by style (mid-century modern, farmhouse, industrial, traditional, minimalist). Each axis produces a topic cluster of 15 to 25 pages that collectively establish the depth AI needs to treat your store as an authoritative source.
Fixture cluster example, pendant lighting: pendant sizing by room type, pendant sizing for a kitchen island, single vs multi-pendant layouts, mini pendant vs standard pendant, pendant bulb base compatibility, pendant Kelvin selection by room, pendant dimmer compatibility, pendant height above a counter, pendant height above a dining table, glass vs metal pendant shades, pendant style guides by design aesthetic. That is 11 pages from one fixture type, each answering a distinct question a shopper or an AI system encounters.
Room cluster example, kitchen lighting: best Kelvin for a kitchen, pendant vs flush mount for a small kitchen, how many pendants for an island of a given length, under-cabinet lighting Kelvin matching, dimmer compatibility for kitchen fixtures, layering ambient and task lighting in a kitchen, fixture finish selection for a kitchen's hardware. Each page targets a real question a kitchen-renovation shopper asks before choosing a fixture.
Style cluster example, farmhouse lighting: farmhouse pendant sizing guide, farmhouse vs industrial chandelier comparison, best bulb shape for a farmhouse cage pendant (a warm-toned filament-style bulb rather than a plain frosted globe), farmhouse sconce placement by hallway width, farmhouse dining room chandelier sizing, finish pairing for farmhouse hardware (matte black or aged bronze rather than polished chrome). A style cluster answers a different kind of question than a room or fixture cluster, not "what size" but "what looks right together," and AI systems retrieve this content just as often when a shopper asks a style-comparison question.
Score your cluster depth against lighting-specific publications currently being cited in your fixture type, room, or style. The gap between your page count and theirs is the topical authority gap AI weighs when deciding whom to cite. A store that has built out all three axes, fixture, room, and style, for its core categories has a structural advantage over a store that only covers one, because a shopper's question can arrive from any of the three directions.
Programmatic Lighting Content
The math for lighting content is multiplicative. Cross your fixture types with room types, cross that with styles, and you get hundreds of legitimate pages. Each one answers a real query lighting shoppers ask AI. "[Fixture type] for [room] in [style]" generates pages like: pendant lighting for a farmhouse kitchen, chandelier for a mid-century dining room, sconces for a traditional bathroom, flush mounts for a minimalist entryway.
Each combination is a distinct search intent. Someone asking "pendant lighting for a farmhouse kitchen" wants different guidance (warm finishes, glass or metal shades, cage or lantern shapes) than someone asking "pendant lighting for a modern kitchen" (clean lines, matte black or brass, geometric shapes). The page has to address that specific intersection, not swap a style keyword into a generic sizing template.
This is where a programmatic content approach changes a lighting store's citation surface. Instead of hand-writing 200 pages, you build a template architecture where the fixture type, room type, and style all pull real sizing rules, bulb specs, and Kelvin guidance rather than generic filler.
Lighting content is well suited to a programmatic approach because the variable dimensions, fixture type, room type, style, bulb base, and Kelvin range, are well-defined and finite. A store with 8 fixture types, 6 room types, and 5 styles has 240 potential pages, each answering a query a real shopper asks AI before buying.
Your 30-Day Plan
Week 1: Technical foundation. Audit your robots.txt and confirm AI crawlers are not blocked. Add Article schema with a credentialed author to existing content pages. Implement Product schema with bulb-base, wattage, socket count, and dimension properties on every fixture page. Add FAQPage schema to any page answering sizing or bulb questions. Set up an author bio page with Person schema and real fixture experience described in the bio. Run a technical audit to catch crawlability gaps before you publish new content on top of them.
Week 2: First cluster pillar. Pick your highest-volume fixture type or room, identifying which sizing or compatibility queries in your category are weakly answered right now. Write one comprehensive pillar page, 2,500-plus words, with real sizing formulas, a bulb-compatibility table, and Kelvin guidance. This becomes the hub of your first cluster.
Week 3-4: Supporting pages. Build 10-15 supporting pages around your pillar. Each answers one specific sizing, bulb, Kelvin, or dimmer question from your cluster map. Interlink them to the pillar and to each other. Add Article, FAQPage, and where relevant HowTo schema to each.
By day 30 you will have a technical foundation AI can crawl and trust, plus a 12-16 page cluster establishing authority in one fixture type or room. Citations from this cluster typically begin appearing at 30 to 60 days. Scale to your next cluster and repeat, moving to the next fixture type, room, or style axis each cycle until your sizing, bulb, and Kelvin content covers every combination your store actually carries.
Two Ways to Close This Gap
Do it yourself
Research the sizing and compatibility questions your buyers actually ask, write the pillar page and supporting sizing and Kelvin guides with real formulas, add the schema, and interlink everything. This works if you have the time and the technical knowledge to write it accurately. Most lighting store owners are busy with sourcing and merchandising, not writing bulb-compatibility tables.
Let Ollie do it in 48 hours
Tell Ollie what you sell and it builds the cluster directly. Pillar page, supporting sizing and compatibility content, schema, and internal linking, grounded in your actual product specs rather than generic copy. Same destination, a much shorter timeline.