Capability pages that turn an engineer’s search into an RFQ

An engineer in Stuttgart needs 200 shafts turned from 42CrMo4 steel to ±0.01 mm, delivered within six weeks. She types roughly that into Google and opens three supplier pages in tabs.

The first shows a slogan and a list of twelve services. The second offers a 14 MB catalogue to download. The third has a spec table, a lead time, photos of real parts and a form that takes her STEP file. The third one gets the RFQ.

Engineers rate a well-kept website 4.0 out of 5 as a sign of a credible supplier, against 2.8 for a trade show sponsorship (TREW Marketing, 2025). In my experience, the page doing the convincing is rarely the homepage. It is the product or capability page they land on from a search for a part, a machine, a material or a process. This article is about building that page.

What engineers look for before they contact you

Technical buyers get through 62% of the buying process online before they engage with sales (TREW Marketing and GlobalSpec, 2026). What they read in that time is specific, and it is not marketing copy.

Datasheets top the list at 79%. In-depth blog posts sit at 10%. And when engineers do contact a salesperson for the first time, 40% say a price or stock question is what made them do it. Each of those calls is a question your page could have answered, from a buyer who could have sent an RFQ that same evening.

I cover the wider journey in how industrial buyers choose suppliers. Here I stay with the one page where that journey turns into a request.

Where Bulgarian industrial sites fall short

Eurostat’s 2025 data shows the size of the gap. Only 38.7% of Bulgarian companies with 10 or more staff have a website that describes their products or lists prices, against 66.4% across the EU. Among manufacturers, 32% have a site in two or more languages, against 41.6%.

The same numbers are your opening. In many Bulgarian niches, the first page of Google is held by directories and thin catalogue pages. A clear page with a spec table does not need to beat fifty strong competitors. It needs to be clearer than five weak ones.

One page per capability, named the way buyers search

Engineers rarely search for a company name. They search for “Lufkin gearbox repair”, “5-axis machining titanium”, “laser cutting stainless 12 mm” or a part number. Google ranks pages, not companies, so each of those searches needs a page of its own with a heading that matches it.

• Dealers and repairers: brand, model and service. “Falk gearbox repair and overhaul”.
• Job shops: process, material and tolerance or size. “CNC turning of stainless steel parts to ±0.01 mm”.
• Machine builders and integrators: machine type and the job it does. “Robotic palletising cell for 25 kg bags”.

An industrial repair company in Texas I worked with had decades of shop-floor expertise and a website that did not show it. Over a year I tuned its service pages for gearbox repair, overhaul, exchange and pump repair, and built brand and model pages for Falk, Western, Philadelphia Gear and Lufkin gearboxes. By January 2023, 29 of its keywords were in Google’s top 10, with #1 for “gearbox overhaul”, “industrial gearbox repair”, “gear hobbing services” and “gearbox repair services”. Leads grew from 234 to 800 in a year.

Speed work and link building helped too, so I do not give the pages all the credit. But a search for “gearbox overhaul” can only rank a page that is about gearbox overhaul.

The rule also works in reverse. When two of your pages chase the same search, both usually lose. ITCE’s ServiceNow content was spread over several pages, and after I consolidated them into one hub, organic visits to those pages rose 192%. Playbook 2 shows how to pull buyer searches from your own Search Console data and give each one a page, and only one.

Capability pages also need a way in. Alcatraz AI, which sells facial authentication for access control, more than tripled its organic conversions in 12 months with a 25-page site revamp and a blog built around buyers’ questions. In Texas, a guide called “What are centrifugal pumps used for” became the second biggest landing page after the homepage. Guides bring the reader in; the capability page is where they ask for a quote.

The anatomy of a page that wins RFQs

This is the structure I use, whether the page is for a gearbox repair shop, a sheet metal subcontractor or the dealer of an Italian packaging machine. Not every page needs every row. But each missing row is a question the engineer has to email you about, and many will not bother.

On price: most owners will not publish a price list, and for custom work you cannot. “Price on request” is fine if it comes with something useful: a typical range, the minimum order, or what drives the cost. An engineer who can see the order of magnitude sends the RFQ. One who sees nothing often calls the supplier who answered the question.

On specs: put them on the page as text, not only in the PDF. Engineers skim tables, Google reads them, and AI assistants such as ChatGPT and Perplexity build their supplier shortlists from pages that state facts plainly. Playbook 3 shows how to check whether they name you.

A short RFQ form that accepts drawings

The form is where most capability pages lose the engineer. A box for name, email and message tells them the drawing will need a separate email, a reply and a wait. Ask only what you need to prepare a quote, and capture the rest automatically.

The hidden fields matter more than they look. Without them you cannot tell which page produced which RFQ, and you end up judging pages by traffic. Playbook 1 covers the setup in GA4 and Tag Manager.

Then count requests, not submissions. At ITCE, forms sent from organic and AI search rose from 303 to 423 in 90 days while confirmed leads dipped from 87 to 76, so a monthly check against the CRM is now part of the routine. A form only counts as a lead when it is a real request from a company that fits the customer profile.

Write the page in your buyer’s language

If you export, your buyers in Stuttgart, Bucharest or Thessaloniki search in German, Romanian and Greek, and they compare suppliers on the pages they can read. Among Bulgarian machinery makers, 49.6% have a site in two or more languages, against 68% across the EU. In the sites I audit, the second language often stops at the homepage.

Google’s documentation is practical here. Google uses the visible content of a page to decide its language, and it recommends a separate URL for each language version rather than switching language with cookies or browser settings. So a German buyer needs a real German page at its own address: German H1, German spec labels, a German form.

Start with the market that already sends you enquiries, and with your best-margin capability. Have a native speaker check the heading, the table labels and the form. Machine translation gives you a draft, not a page, and one wrong technical term tells an engineer you have not worked in their market.

What to do this week

1. Open Search Console and list the searches that already show your site for a brand, model, process or material you sell. Each one is a page you need.
2. Pick the capability with the best margin and check its page against the table above. Count the missing rows.
3. Add a spec table as text, a lead time and a file upload to that page, with hidden fields for the page and the source.
4. If you split one “Services” page into several, redirect the old URL to the closest new page. Rebuilding a website without losing rankings explains how.
5. After 60 to 90 days, count RFQs per page, not visits.

If you would rather I build the first pages with you, book a call below.