Landing pages that run alongside your shop — not inside it.
Your shop system stays untouched: no plugin, no template changes, no update risk. Alongside it, static pages are built that load fast, deliver structured data and are quotable for AI search. Afterwards you maintain the texts yourself.
Shop systems are built to sell, not to be found.
Retrofitting inside the shop vs. building alongside.
Both routes lead to landing pages. Only one of them survives the next shop update without debate.
What is actually delivered.
Every point below is implemented in the ImkerPur project and publicly verifiable — none of it is planned or in preparation.
Static alongside the shop
Plain HTML in a subfolder of your domain (e.g. /lp/). No plugin, no template changes. Works with JTL, Shopware, WooCommerce and virtually any shared hosting.
Structured data (schema.org)
Organization, Product with brand, AggregateOffer and AggregateRating plus FAQPage. Prices and ratings become machine-readable — the price range is calculated from the real shop prices.
Visibility in AI answers (GEO)
llms.txt describes shop and pages for LLM crawlers. Each page also carries a quotable direct-answer block — the format AI search engines prefer to adopt.
FAQ from real search queries
The questions come from your shop's Google Search Console — from what people actually type. No keyword guessing.
Performance & Core Web Vitals
WebP with responsive srcset and lazy loading, CSS inlined into the HTML, self-hosted fonts — no Google Fonts request, which also keeps it clean from a privacy standpoint.
Accessibility with calculated contrasts
Colour values are not estimated but calculated and documented in the code. For ImkerPur the brand orange was deliberately shifted to a darker button tone so white text reaches the AA threshold.
Auto-deploy (CI/CD)
Push → build → upload via SFTP into the target folder. Deliberately without a delete flag: it only uploads into its own folder, never removes anything from the shop.
Maintain it yourself instead of reordering
An editing mask shows only the fields you should change — in plain language instead of code. Email login, no developer account, no recurring costs. After saving, the change is live about two minutes later.
AI copywriter with legal guardrails
You describe in plain language what should change and receive finished text plus the field it belongs in. Your industry's legal limits are built in — for food, for example, the Health Claims Regulation, LMIV and UWG. Impermissible requests are explained and replaced with compliant wording.
Three options.
All prices one-off and excluding VAT. What remains as running cost: your web space, which you have anyway. No licence or usage fee to us — you receive the repository with all content.
For shops that first want to see whether the format works for them.
The scope delivered for ImkerPur — including self-service maintenance.
For larger ranges that want to cover many product groups.
From access credentials to handover.
The timings are empirical values from the ImkerPur project (first commit to go-live: 7 days), not a contractual commitment. The bottleneck is almost always content approval, not the build.
Assessment
Shop system, hosting and access are checked: where is the docroot, what does the .htaccess do, which subfolder is free? Before any intervention, the current state is backed up.
Topics & questions
Page topics come from the product groups, the FAQ blocks from real Google Search Console queries — not from invented wish-list keywords.
Design alignment
The pages adopt the look of the existing shop (colours, type, button style) so there is no visual break. Contrasts are recalculated to WCAG AA in the process.
Build & delivery
Astro builds static HTML. The upload goes via SFTP exclusively into its own subfolder — the shop itself is untouched, no file outside the target folder is changed.
Handover
Editing mask, guide and auto-deploy are in place. From then on you change texts yourself; every change is live within minutes.
What shop owners want to know beforehand.
If your question is not here, ask it in the intro call — that costs less time than a project that helps no one.
Does my shop have to be rebuilt for this?
Which shop systems are supported?
What happens when my shop gets an update?
Can I change the texts myself later?
How much additional revenue will this bring?
How long does it take?
What is GEO and why does it appear next to SEO?
Who owns the result?
More on visibility for shops.
Background on performance, search engines and AI visibility in e-commerce.
E-Commerce Trends 2026
Social commerce, AI personalisation and headless: the key trends for online retailers.
Read more
Core Web Vitals: WordPress vs. Next.js
Performance comparison: which framework delivers better load times for your shop?
Read more
Scaling for SMEs
How mid-sized companies scale their online business profitably.
Read moreIs this right for your shop?
In the intro call we look at your shop system, your hosting and your product groups. If the format brings you nothing, we will say so.
