Interior Design Project Page SEO

The leverage compounds across three dimensions. Discoverability — each project page is indexed separately and ranks separately, so the studio's total searchable surface area scales with project count rather than capping at "one portfolio page". Specificity — each project carries its own named style, location, and project type, so each is a citation target for that specific constraint stack rather than competing as one generic surface for every constraint. Authority — each project page is a node in the studio's internal link graph, which means citations to one project earn ranking benefit for the studio's home page and the principal designer's bio page through the standard PageRank-style flow. The single Portfolio page captures none of these.

The honest counter-argument is that some designers genuinely have only six or eight publishable projects, and a parent-plus-individual-page structure feels over-engineered for that catalogue depth. The arithmetic still favours the structure. Six discrete project pages is six citation targets; one Portfolio overview is one. Even at low catalogue depth, the citation multiplier is real. The right time to defer the structure is when the studio is genuinely pre-launch with no completed projects yet — in that case, the right move is to ship a Coming Soon Portfolio page, do the work on the next two projects with project-page hygiene from day one, and never write the single-Portfolio version in the first place.

The order matters. AI engines extract from the first 200 words of the page, which means the title plus the hero caption plus the opening lead is the entire extraction window. A project page that puts the hero gallery above the lead — the visual instinct most designers have — loses the citation because the engines see a sequence of img tags before they see any extractable text. The fix is structural: hero image goes first (one image, with caption), then the lead (134-167 words, named style and location and designer), then the gallery (the remaining images with proper alt text). Visually this is one large hero plus a body plus a gallery, which is also the editorial-design pattern Architectural Digest and Domino use on their project features.

The credits block at the end of the page is small but disproportionately valuable. AI engines weight named-source attribution heavily — a project page that credits the photographer by name (with a link to the photographer's site), the principal designer by name (with a link to the bio page), the contractor by name where known, and any publications the project appeared in (Charleston Magazine's Best Of 2025, House Beautiful's Next Wave 2024) reads as a documented and verifiable creative work. A page that lists only the studio name reads as marketing prose, and the engines weight it accordingly. The credit block costs five minutes per project page and meaningfully shifts the engine's confidence in citing the page.

Google's structured-data documentation⁶ notes that CreativeWork does not currently trigger a specific rich-result card type in Google search — there's no "creative work" star rating or special card. The value of the schema is entity recognition rather than rich-result eligibility. AI engines (ChatGPT, Perplexity, Gemini, Claude) read JSON-LD blocks as authoritative declarations about what the page is about, and a CreativeWork block on a project page tells them: this page documents one specific project, by this specific designer, in this specific location, in these specific named styles. That structured signal makes the page meaningfully easier to cite confidently for style + location queries.

 <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "CreativeWork", "@id": "https://yourstudio.com/projects/tradd-street-residence/#project", "name": "Tradd Street Residence", "description": "Whole-house Coastal Modern renovation of a 1920s Charleston single house. Custom oak built-ins flank a reclaimed shiplap fireplace; linen-and-rattan furnishings carry through the main floor; the kitchen plan was redrawn around the original chimney mass. Completed 2024 for a young family of four.", "keywords": "Coastal Modern, whole-house renovation, custom millwork, 1920s Charleston single house, reclaimed shiplap, linen and rattan", "locationCreated": { "@type": "Place", "name": "Charleston, SC" }, "dateCreated": "2024-09-01", "creator": {"@id": "https://yourstudio.com/#principal"}, "image": { "@type": "ImageObject", "contentUrl": "https://yourstudio.com/s/coastal-modern-charleston-living-room-built-ins.jpg", "name": "Tradd Street Residence — living room hero", "caption": "Coastal Modern living room in Charleston with custom oak built-ins and reclaimed shiplap fireplace.", "creator": { "@type": "Person", "name": "Margaret Wright" } } } </script> 

Three details inside the block do disproportionate work. The keywords field is where the named-style vocabulary is declared formally — comma-separated, named styles plus material vocabulary plus project context. The creator @id reference points back to the studio's principal designer Person schema (declared once on the bio page or in the site-wide header injection), which means the engines can walk from the project to the designer to the studio without re-declaring the entity. The image.creator field credits the photographer by name, which is the citation signal that graduates the project page from "marketing claim" to "documented work with named attribution".

The honest framing is that the named-style vocabulary feels uncomfortable to many designers initially. The instinct in design writing is to describe palette and material rather than to slot the work into a named genre, and "Coastal Modern" reads as a Pinterest taxonomy term rather than a craft description. Both feelings are accurate. The terms are imperfect, the boundaries between named styles are fuzzy, and the studio's actual work usually crosses multiple named styles in one project. The SEO discipline is to pick the dominant named style honestly (the one a stranger would identify the project as), use that term consistently as the primary, and use a secondary named style if the project genuinely combines two (Coastal Modern + Biophilic on the same project page is fine; "modern with natural elements" loses the citation).

The keywords property³ in CreativeWork is the formal declaration of the vocabulary for a given project. A studio with ten project pages will have ten different keywords strings — one per project — and the union of those strings is the studio's full vocabulary surface. That union should match the Person.knowsAbout array on the principal designer's schema, the alt-text vocabulary across the gallery, and the named styles the studio talks about in journal posts and About-page copy. The vocabulary discipline is a small cross-page audit, not a big content rewrite, but it is the audit that compounds the citation flow over the next twelve months.

The anchor text choice matters more than the link count. Link to the project page from elsewhere using the project name itself as the anchor ("the Tradd Street Residence"), not a generic phrase ("read more"). Link back from the project page using the designer's name and the studio's name as anchors. This is the standard internal-linking discipline applied with named-vocabulary rigor — every internal link is a small additional confidence signal in the engines' entity graph, and named anchor text shifts the signal from "page links to page" to "named entity links to named entity". The compounding effect over a 10-project portfolio is real and is the structural reason directory profiles outrank designer sites with sparse internal linking, even when the designer's content is better.

The cross-link from related project pages is the highest-leverage of the six. A studio with three Coastal Modern projects should cross-link them mutually — Project A's body section names Project B and Project C and links to them, Project B does the same back, Project C does the same back. This creates a small content cluster of three pages mutually attesting to the studio's Coastal Modern expertise, and AI engines read the cluster as much stronger evidence of named-style specialism than three isolated project pages would be. Apply the same pattern to projects that share a location (three Charleston projects mutually linking) — the location cluster reinforces the local SEO surface in addition to the AI citation surface.

The voice question is genuine. The temptation is to write the lead in the language Architectural Digest features tend to use ("a serene retreat that whispers coastal sophistication" — every word generic, no named style, no extractable passage). The fix is to write the lead the way the principal designer would actually describe the project to a curious dinner guest — short sentences, named style stated plainly, one specific design move that a designer would actually notice ("we redrew the kitchen plan around the original chimney mass" — concrete, specific, attributable). The engines reward the concrete language for the same reason a curious dinner guest would; press-release prose loses to dinner-guest prose in both audiences.