ListingOK v2: marketing site

The challenge

The first version of listingok.com was the front door to the app: home, login, and not much more. Enough for the first customers, but not enough to grow through Google search. The site didn’t tell the story, didn’t segment by user type (property manager vs. hotel vs. independent host), and the entire SEO effort sat on a handful of static pages that competed against each other.

The brief for v2 was to treat the site as an acquisition product, not a landing page. It needed three things. First, new content every week (blog, resources and case studies), so people would come back and link to it. Second, per-market pages in English and Spanish, generated programmatically to cover searches like "Airbnb occupancy {city}". And third, a measurable funnel from first visit to signup, with different CTAs for each segment and each block.

What we built

• Full redesign of the public site: new home, capability pages (pricing, channel manager, market insights, analyzer), segment pages (property managers, hotels, partners) and a reusable component system that lets us assemble new landings in hours.
• Per-market programmatic SEO: auto-generated pages with occupancy, ADR and RevPAR by city, fed by the same pipelines that supply the in-app product. One base per language, indexable and linked from the blog.
• Bilingual editorial hub: blog and resources in EN and ES with separate routes (/en/..., /es/...), full hreflang and per-language sitemaps (sitemap-en.xml, sitemap-es.xml). No machine translation: the content is written in each language.
• Analyzer as the front door: the free tool sits in the hero and in the footer of the site, with its own measured funnel, from click to result and from result to signup.
• CTAs instrumented from day one: every button carries data-event and data-source attributes to distinguish "signup from hero", "signup from pricing" and "signup from use case". Marketing decides where to put the next euro using data, not intuition.
• Public pricing and comparison pages: they are public on purpose, to close the sale sooner. Whoever arrives on a call has already seen the prices.
• Schema.org and metadata consistent across each template (SoftwareApplication, Article, FAQPage where applicable) to feed rich results.

Technical decisions that mattered

1. React SPA with real SEO, not "SPA and pray"

We kept the app’s technical base (React + Vite, served by Express) but treated the public site as a separate use case: pre-rendered routes for indexable content, index fallback for deep links, and a separate build that doesn’t drag the app bundle along. Result: Google’s bot sees full HTML, the user only loads what they need.

2. Programmatic SEO sharing data with the product

The per-city market pages aren’t a marketing verticalisation: they use the same ingestion pipelines that feed the Market Insights dashboard inside the app. One source of truth, two consumers. When a new market is added to the product, the site gains indexable pages for free.

3. Bilingual for real, not Google Translate

Each page lives in EN and ES with localised URLs (/es/precios/ vs. /en/pricing-revenue-management-software/), reciprocal hreflang and separate sitemaps. The blog and resources are written in each language. Consequence: each article doubles the SEO surface without doubling the content team.

4. CTAs as a first-class metric, not an afterthought

Every "Start free", "See pricing", "Try the Analyzer" button carries data-event="cta_signup" / data-source="hero_home". That shows which block on which page brings each signup, without working it out later from heatmaps. Rule: if a metric drives the roadmap, you measure it from version one.

5. A component system for scaling landings

Hero, feature block, testimonial, comparison, FAQ, contact strip: each piece is a component. A new landing (a use case, a partner, a campaign) gets built in hours, not days, while keeping the same typography, spacing and CTAs as the rest of the site. Visual consistency stops depending on the discipline of whoever assembles the page.

Outcome

v2 of listingok.com stops being a door and becomes an acquisition engine: the site publishes editorial content every week, the per-market long tail enters Google with pages competitors don’t have, and the funnel from first visit to signup is measured button by button. Internally, building a new landing is a matter of putting existing pieces together. Testing a new message costs little, which is why more messages get tested.

The most underrated decision in hindsight: sharing data between product and SEO. The per-market pages aren’t a marketing add-on: they’re built from the same data the manager already sees in the dashboard. That single decision turns every product improvement into an SEO improvement at no extra cost.