An engineer looking for a display module rarely starts with “e-paper display.” They type something closer to “2.9 inch e-paper 296x128 SPI” or a part number copied from a previous bill of materials. If the product page is titled “Small E-Paper Module — Best Quality” and the model string only appears inside a downloaded PDF, the page has little chance of matching that query, even when the module is exactly what the buyer needs.
The fix is not a longer keyword list. It is deciding what identifies the part, then writing the page so a person and a search engine can connect the query to the same item.
Start from the strings buyers already use
Collect the names that appear in real enquiries, distributor listings, sample requests and the manufacturer's datasheet. For a display module these usually fall into four groups:
- Model or series: the manufacturer's part number and any suffix that changes the connector, temperature range or driver.
- Physical format: diagonal size, resolution in pixels, active area, outline dimensions.
- Electrical interface: SPI, I2C, parallel, MIPI, RGB, and the logic voltage range.
- Use condition: operating temperature, refresh behaviour, touch option, frontlight or protective cover.
Write these down before touching the page. If two people in the company use different names for the same module, the page will inherit that confusion.
Put the identifying string in the title and first screen
A useful title names the product and its differentiating values. “2.9-inch E-Paper Module, 296×128, SPI, 3.3 V” tells a buyer more than a slogan, provided every value is true for that exact item. Google's guidance on title links explains that search can rewrite or truncate a title, so the page itself must still make the product clear.
The same string should appear in the opening paragraph and in the specification table. Do not rely on the model number being present only in an image, a filename or a PDF attachment. A buyer comparing three tabs needs to see the number without opening anything.
Build a parameter table that can be compared
A table is useful when each row answers a question the buyer would otherwise email you about. Keep the units and test conditions next to the number, and distinguish a guaranteed limit from a typical value.
| Item | What to publish | Common gap |
|---|---|---|
| Part number | Full orderable code and connector suffix | Only the series name |
| Resolution | Horizontal × vertical pixels | “High resolution” |
| Interface | Bus, pin count, logic voltage | “Supports MCU” without levels |
| Operating range | Temperature and humidity conditions | A single “industrial grade” label |
| Refresh | Update time and the condition measured | One number with no test setup |
If the datasheet gives a range such as 2.4–3.6 V, publish the range rather than picking the middle. If a value is a design target rather than a measured result, say so. Precision that is not supported by the source document is worse than a plain, accurate description.
Give each orderable variant its own page
Modules that differ only by a connector, FPC length, touch layer or temperature grade are separate purchasing decisions. A single page that lists eight options in a dropdown makes it hard to link to the exact item, and it makes comparison between two tabs unreliable.
Create one page per orderable configuration when the difference affects fit, price or availability. Keep a series overview page for buyers who have not chosen yet, and link from it to each variant. This also gives sales a stable URL to send in a quotation.
The broader method for organising model and parameter vocabulary is described in this guide to model-word and parameter-word pages for industrial B2B sites. It is written for manufacturers working with large catalogues, and the same logic applies to a display line with dozens of size and interface combinations.
What to remove before publishing
- Invented model numbers created to catch search terms. They mislead buyers and break the link to the datasheet.
- Long lists of interfaces or sizes the module does not support.
- Copied datasheet lines with the units stripped out.
- “Customisable” without saying which parameters can change and what the minimum order is.
A short pre-publish check
- Can an engineer identify the exact module from the title, first paragraph and table alone?
- Does the part number on the page match the current datasheet revision?
- Are units and test conditions present for every numeric claim?
- Does each variant have a URL that can be quoted in an email?
- Is the datasheet linked as a separate file, with its revision date shown?
A display page does not need to rank for every combination of size and interface. It needs to be the page that answers the query for the part a buyer already has in mind. Naming the item accurately is the part of that work that no amount of link building can replace.