InLog builds the boards engineers still need. The web just cannot find them.

What InLog is, in one read

InLog is a manufacturer whose customer is the embedded design engineer and the OEM integrator, not the end consumer. Everything it sells reduces a customer's redesign risk by keeping legacy interfaces and long-lifecycle boards available when bigger vendors move on.

Who actually specifies and signs

Embedded board deals are engineer-led and global. The specifier is a design engineer choosing a form factor; the economic buyer is an OEM procurement or product lead; the gatekeeper is a sustaining engineer protecting a long product lifecycle; the channel is the distributor who shortlists suppliers.

A long-lifecycle niche, told as a plain product list

InLog's strongest positioning - "the dependable Taiwan source for long-lifecycle embedded boards and legacy form factors others have dropped" - is genuinely differentiated. The gap is that the site does not claim it; it lists boards without the lifecycle, compatibility and supply promises that this exact buyer is searching for.

Voice and USP

The current voice is spec-only and functional, strong on board details, silent on the buyer outcome that matters most: continuity. Differentiators worth amplifying: availability of ISA and PC/104 form factors mainstream vendors have discontinued, low-power fanless x86 designs, board-level OEM/ODM flexibility from a focused Taiwan factory, and pin- and interface-level compatibility for sustaining engineers. The shift needed is from "here is a board" to "here is the board you cannot get anywhere else, available for years, with the datasheet one click away."

SWOT

A product list that stops short of converting

The site presents boards and specs, but it asks the visitor to email before giving them the datasheet, and gives the self-directed engineer little to download, compare or trust.

Information architecture

The structure is a flat catalog: product categories and individual board pages with spec tables, plus a contact route. It reads as functional but dated, with limited English depth and no decision-stage assets, no downloadable datasheet library, no product selector, no lifecycle/availability page, no application notes. For an engineer who is researching but not ready to email, there is no self-serve path, and crawlability appears weak, which compounds the SEO gap in the next section.

Five quick wins, ranked by impact / effort

1. Install a real analytics stack (GTM + GA4 + retargeting tags). High impact / Low effort
   No visible tracking means no funnel data, no retargeting audiences, and no way to prove what marketing produces.
2. Publish a crawlable English datasheet hub with downloadable PDFs. High impact / Medium effort
   Engineers search for and download datasheets before they ever email; indexable spec pages are the single highest-leverage content fix.
3. Add a low-commitment CTA beside "contact us." High impact / Low effort
   "Download the datasheet" or "Get the EOL-replacement guide" captures researchers who will not send an RFQ yet.
4. Build a board / form-factor selector and lifecycle page. Medium impact / Medium effort
   A guided selector plus a clear long-lifecycle commitment reduces friction and becomes a retargetable engagement event.
5. Add trust scaffolding near every CTA. Medium impact / Low effort
   Surface lifecycle/availability commitments, certifications, and named application examples so the inquiry feels earned.

The category is searchable. InLog mostly is not.

Design and sustaining engineers actively search for "PC/104 SBC," "ISA bus CPU card," "low power x86 SBC" and "long lifecycle embedded board." These are commercial, high-intent terms - and InLog has limited ranking presence and little crawlable English content built to capture them.

Priority keyword opportunities (volumes are directional estimates, not measured rank)

Technical and structural notes

High-level signals only (no privileged audit access): the site appears dated and content-thin, with limited English depth, likely weak crawlability and minimal structured data. Datasheets that should be indexable PDFs appear gated behind contact. There is no detectable analytics/tag stack. Core Web Vitals are N/A without a measured run; a Lighthouse pass should be step one. The strategic gap is not exotic - it is missing crawlable English product and datasheet content matched to category queries, plus AEO formatting so AI assistants cite InLog when an engineer asks "who still makes PC/104 boards" or "ISA CPU card supplier."

Backlink and authority prospects

Earn category authority via: (1) embedded trade media (Embedded Computing Design, Electronics Weekly, EDN), (2) distributor and marketplace listings (Taiwantrade, oemsecrets, component catalogs), (3) EOL and obsolescence-management communities where sustaining engineers shortlist sources, (4) PC/104 and embedded-form-factor reference directories, and (5) maker and legacy-hardware forums where niche board demand surfaces.

A field of larger Taiwan IPC brands that out-publish InLog

InLog competes on niche form-factor availability and long lifecycle, but loses the upstream discovery battle to established Taiwan industrial-PC brands that have invested for years in English content and category SEO.

Direct competitors

ICOP Technology - the closest match: PC/104 and small-form-factor SBCs (DM&P Vortex86), strong English catalog and content. ADLINK - broad embedded boards and modules, deep documentation. IEI Integration - SBCs, panel PCs and industrial boards with heavy product SEO. Avalue - embedded boards and systems with full English datasheet libraries. Axiomtek - embedded and SBC range with strong web presence.

Aspirational competitors

Advantech - the benchmark for industrial-computing content marketing and category authority. congatec - the reference brand for computer-on-module documentation and developer trust. Kontron - premium embedded platform brand with strong lifecycle messaging.

Traffic and DR are public-dataset estimates for illustration, not measured analytics. InLog values are unverified and likely low given the thin organic footprint.

A real niche, almost entirely unpublished

InLog has the raw material for a defensible content position - genuine long-lifecycle expertise and form factors others abandoned - but publishes only bare spec pages rather than the lifecycle, compatibility and selection answers its buyers search for.

Current content is limited to product/spec listings; there is no blog, no application notes, no comparison or selection content, and no detectable, active social presence (counts N/A). For a board-level B2B supplier, the natural channels are an indexable datasheet library, an EOL/obsolescence resource, and LinkedIn for distributor and OEM reach. The engagement gap: nothing speaks to the sustaining engineer protecting a 10-year product, and nothing in English explains why an OEM should second-source through InLog. Tone is purely technical; it would convert far better with explicit lifecycle promises, compatibility proof, and short, downloadable selection guides.

90-day editorial calendar

Build the funnel before you scale spend

With no tracking detected today, the first move is measurement, not budget. Once GTM, GA4 and retargeting tags are live and audiences are building, a tight, low-cost TOFU-MOFU-BOFU program can capture this high-intent, low-competition niche efficiently.

Minimum viable stack

GTM container, GA4 with key-event tracking on datasheet downloads, selector use and contact/RFQ submits, a LinkedIn Insight Tag for distributor and OEM audiences, and a Meta Pixel for retargeting reach. Wire CTA clicks to events so every later optimization is data-driven.

Google Search ad copy

Meta / LinkedIn ad concepts

From relationship-led to demand-led in 90 days

North-Star metric: marketing-sourced qualified RFQs per month (quote requests and distributor inquiries). Everything below ladders up to making inbound search a reliable, measurable pipeline source alongside existing relationships and distributors.

Priority matrix

The team that turns this report into pipeline

Questions an InLog leader would ask first