People shopping for a desk often start with a measurement. They have an alcove of 110 cm, a box room, or a corner that needs an L-shape facing a particular way. Chair buyers start with a problem: a sore back, long working days, a tall frame. Office managers start with a headcount and a deadline. Each group searches in its own terms, and each runs into a different weakness on a typical home office furniture site.

This guide applies Google’s documentation to those problems. Google’s rules are linked to the page they come from. Where I am giving my own view, I make that clear.

Searches that start with a size

Width is often the first filter a desk buyer reaches for, and it shows up in search phrases too: “120 cm desk”, “small desk for bedroom”, “deep desk for two monitors”. Corner and L-shaped desks add handedness, and a buyer who needs the return on the left has no use for a right-handed page.

My advice is to give the size bands that people actually search for their own category pages, with copy that explains what fits where: compact desks for alcoves, standard widths for one monitor, wider tops for two. Write the measurements on every product page as text, including depth and height range, not only in a diagram.

For handedness, check how your platform stores it. Google’s variant markup lets variesBy name colour, size, material, pattern, suggested age or suggested gender, so left and right have no value of their own. Where a left-hand and right-hand version share a page, I would name the hand in the variant title and its sku. Do not relabel it as a colour or size difference just to fit the markup. Where they are sold as separate products with separate codes, give them separate pages that link to each other.

Standing desks: frames, tops and finishes

Height-adjustable desks multiply quickly. A frame in black, white or grey, a top in several widths, and a top finish in oak, walnut, white or black can give dozens of combinations from one product. A desk builder that writes every choice into the URL can create thousands of crawlable addresses.

Google’s URL structure guidance says each variant should be identifiable by its own URL, as a path or a parameter. It also says Google ignores anything after #, so a builder state kept in a fragment is invisible to indexing. That can be useful: fragments are a reasonable home for combinations you never want indexed.

Here is how I would split it:

  • Frame colour and top size as indexable variants. These match real searches and map to the color and size values in variesBy, written as https://schema.org/color and https://schema.org/size.
  • Top finish as material, where the choice is between wood types or laminate.
  • Everything else in the builder, such as cable trays, castors or a memory keypad, as add-ons recorded with the order rather than as variant URLs.

With Google’s single-page set-up, one canonical URL covers the group, and every variant must still be preselectable through its own URL with the correct image, price and availability, ready to add to the basket. Each variant needs a unique sku or gtin, and the group needs its own ID.

Category filters and the crawl

Desk and chair categories filter by width, shape, electric or manual lift, motor count, weight capacity, colour, seat height range and armrest type. Google’s faceted navigation guide notes that crawlers working through every combination can use a lot of server capacity and slow down discovery of new products.

If filtered pages do not need to rank, Google’s suggestions are to block their parameters in robots.txt (keeping product pages and one unfiltered listing open), or to keep filters in a fragment. Pointing a canonical at the unfiltered page or adding nofollow to filter links can help, but Google calls both less effective in the long run.

Some sites build filters into the path, such as /desks/standing/white/. In that case Google asks for a consistent order of filters and no duplicates, and for a 404 at any combination with no products. A white, manual, dual-motor desk that you do not sell should not return an empty page with a 200 status.

Chairs: specs, sizes and fit

Office chair searches are often about fit: “chair for a tall person”, “chair with adjustable lumbar support”, “chair for short legs”. The answers sit in the spec sheet, which some sites show only as an image or a downloadable PDF.

  • Publish seat height range, seat depth, back height and recommended user height and weight as HTML text, so search engines and screen readers can read them.
  • Size variants are genuine variants. Chairs sold in small, medium and large frames fit Google’s size value.
  • Arm, headrest and base options usually suit product page options rather than variant URLs, unless each has its own code and demand.
  • Write fit guidance on category pages. A short paragraph explaining which chairs suit which heights helps both the buyer and the page’s relevance.

Monitor arms, accessories and compatibility

Accessories bring compatibility questions that buyers search for directly. A monitor arm has a VESA mounting pattern, a weight range and a clamp range that must suit the desktop thickness. A cable tray must fit the frame width. A desk converter must suit the desk depth.

Put those numbers in text on both sides: on the arm’s page, the desk thicknesses it clamps; on the desk’s page, the top thickness and whether it takes a grommet or clamp. Linking each desk to the accessories that fit, and each accessory back to compatible desks, gives search engines a clear map and may save a buyer from ordering the wrong part.

Bulk orders, delivery and merchant listings

Small businesses furnishing an office may buy in tens, sometimes on account or after a quote. Google’s merchant listing documentation sets limits that matter here:

  • A buyable page with a price above zero. Pages that only take quote requests do not qualify.
  • One Offer per product, not an AggregateOffer; volume price breaks belong in the page copy or the basket, not in the markup as an aggregate.
  • Shipping policies set once under Organization, overridden per offer where needed: flat-pack delivery for many desks, a different service for assembled chairs or heavy pedestals.
  • Images of at least 50,000 pixels, crawlable, and ideally in 16:9, 4:3 and 1:1.

Google’s image guidance adds that alt text is the most important image metadata. A photo of a desk at standing height deserves alt text that says so, with the height if it is shown: “Walnut standing desk raised to 115 cm with two monitors”.

Seven checks for a home office furniture site

  1. List the desk widths and shapes buyers search for and check each has a page that answers it.
  2. Open a corner desk and confirm the left- and right-hand versions are clearly separated.
  3. Count URLs created by the desk builder in a crawl, and check which ones carry a self-referencing canonical.
  4. Load a path-based filter combination with no products and check the status code.
  5. Confirm that chair dimensions and user height ranges are text, not images.
  6. Check that monitor arm pages state clamp range and that desk pages state top thickness.
  7. Test a bulk-priced product in the Rich Results Test and check for a single Offer.

On the five desk and home office product pages I tested in October 2026, Lighthouse’s SEO checks were mostly clean. Three pages passed all of them. One had links without a crawlable address and another had link text that did not describe its target. If builder options or compatible monitor arms are linked through script rather than real links, crawlers may miss them. Lighthouse’s SEO category is a short technical list, though. It cannot judge desk-size pages, builder URL counts or how chair fit data is shown, which is most of this page.

For speed, including desk builders and chair 360 views, see office furniture website performance. The commercial side is in selling desks and home office furniture online, and for building a desk interactively, see the desk configurator. For business buyers, my B2B ecommerce SEO service goes further, and an ecommerce SEO audit is the usual first step.

Sources

Desk and chair guidance above draws on these Google pages, read in October 2026: