Dev.to WebDev ๐Ÿ›  Dev ๐Ÿ‘ 0 ๐Ÿ“– 4 min read

SEO for a site made of 3D canvases: how 100+ LEGO builds became findable pages

A site whose main content is a 3D canvas has a problem: to a search engine, a canvas is an empty rectangle. Mister Blocks has over a hundred LEGO building guides, and at first Google could see almost none of what makes t

SEO for a site made of 3D canvases: how 100+ LEGO builds became findable pages

A site whose main content is a 3D canvas has a problem: to a search engine, a canvas is an empty rectangle. Mister Blocks has over a hundred LEGO building guides, and at first Google could see almost none of what makes them useful.

This is what I changed so every build is a real, findable page, without giving up the 3D viewer.

The LEGO Truck MOCs category page: a heading, an intro, category chips with counts, and build cards on a wooden table

1. Render the words on the server

Every public page is built by one serverless function. It fills an HTML template with the title, description, headings, links and structured data, so everything a crawler needs is in the HTML, with no JavaScript. Then the page's own script adds the 3D view on top.

There are five kinds of page: the landing pages, the gallery hub, category pages, building guides, and the print booklet. The booklet is noindex; everything else is indexable, cached at the edge for five minutes and served stale for a day while it refreshes.

One early mistake: robots.txt blocked /api/, which is where the build data comes from. Google could fetch the page but not finish rendering it. Removing that line was the first fix.

2. One address per build, made from its name

Guides used to live at /g/<random id>. Now the address follows the name: "Mega Greninja" lives at /builds/mega-greninja-lego-build. Old /g/ and /s/ links, and old names after a rename, get a 301 to the one current address (keeping ?step= so deep links still work). Two builds with the same name get the id added to the second.

3. Titles people actually type

The first titles looked like this:

Mega Greninja LEGO build: free 3D instructions, 205 pieces | Mister Bricks

Nobody searches for my brand. They search for "lego greninja". So titles now lead with the search phrase and drop the brand:

LEGO Greninja MOC: Mega Greninja Free Instructions, 205 Pieces

For each build, a small, cheap Claude call (low effort, 2,000 tokens) picks its categories and the exact phrase people type: lowercase, starting with "lego", 2โ€“4 words. The phrase leads the title, and the build's name follows: a green dragon becomes "LEGO Dragon MOC: Green Fire-Breathing Dragonโ€ฆ", and Freddy Fazbear becomes "LEGO FNAF MOC: Freddy Fazbear, Free Instructions".

The model gets it wrong sometimes. It picks a character's full name when people search for the game, so 57 builds have hand-picked phrases from keyword research that the tagger is never allowed to overwrite. That's why Freddy is under "lego fnaf": that's the phrase people actually search, about 34,000 times a month.

Freddy Fazbear from Five Nights at Freddy's as a brick figure

4. Categories that earn their place

There are 16 categories, from Pokรฉmon and cars to anime, video games and TV shows. Each one lists its target keywords with their monthly search volume right in the code, and its title and heading use them word for word.

A category only goes into the sitemap and gets indexed once it has at least 3 builds. Below that, the page works but is noindex, so Google never sees thin pages.

One category is a rule rather than a tag: easy builds are anything with 100 pieces or fewer (or built from a photo of a real pile). No model needed for that one.

There are also four keyword landing pages for what people search before they know the site exists: LEGO build ideas, LEGO scanner app, custom LEGO instructions, and the home page for "lego ai".

5. Structured data that matches the page

  • Guides are a HowTo: total time from the piece count, up to 40 HowToSupply items from the parts list, one HowToStep per step (each with its own ?step=N URL), and the build's pictures as ImageObjects.
  • Category pages are a CollectionPage with an ItemList of builds, plus a BreadcrumbList and an FAQPage.
  • The home page is a WebSite and a free WebApplication.

Breadcrumbs follow LEGO MOCs โ€บ category โ€บ build, and each guide ends with related builds from the same category and a link to its "twin" (the small playable version โ†” the big voxel sculpture).

Son Goku from Dragon Ball as a brick figure
Son Goku: 143 pieces, 14 steps, in anime.

6. Pictures for Google Images

A 3D canvas has no image to index. So every build is rendered once by the real viewer, on a photo of a wooden table, at 1600ร—1200, and stored in R2. Those renders are the og:image, they're in the JSON-LD, and they're in the image sitemap, every picture of every build. The one picture that is never published is the photo someone uploaded with their idea; it might not be theirs to share.

7. Tell the search engines

The sitemap lists every page once per language with the full set of hreflang alternates (more on the Ukrainian version in another post). A tiny script posts every URL to IndexNow, so Bing and the others hear about new builds the same day.

Kirby as a pink brick figure on green grass

What I'd tell myself on day one

Treat every 3D object as a page first and a canvas second: a name, an address, a title in the words people search, a picture, and a few honest lines of text. The 3D view is what makes people stay. The page around it is what lets them find it.

Browse it the way Google does: start at the full gallery or any category, like robots, movies or famous people. Or snap your own bricks at misterblocks.com.

Unofficial fan builds. LEGOยฎ is a trademark of the LEGO Group, which does not sponsor or endorse this site. Characters and brands belong to their owners.

๐Ÿ“ฐ Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes โ€” full credit and traffic to the original publisher.