For Jome Journey, a Singapore property business, I build Google Ads landing pages for property launches in WordPress and Elementor, written to ad policy from the first line. Since July 2023 the work has included rebuilding an enquiry site after an earlier one was suspended by Google Ads, and building a reusable section library used across multiple launches.
The problem
Property launch pages exist to collect enquiries from paid ads. Google Ads has strict rules about what such pages may say and how they collect personal data. A page that overstates, hides who is behind it, or pre-ticks consent risks the account, not just the campaign.
Before I worked on it, an earlier enquiry site had been suspended by Google Ads. Each new launch also needs its own page, quickly, without starting from zero or breaking what came before.
Constraints
- Ad policy first. No prices, availability, distances or urgency claims unless officially released.
- Clear disclosure. The page must say it is not the developer's website and show the salesperson and agency details.
- Consent done properly. The enquiry form uses an unticked consent box.
- Editable and visible. Content must show in the Elementor editor and render without JavaScript.
- Every device. Pages are tested on desktop, tablet and mobile.
What I built
A rebuilt enquiry site
I rebuilt the enquiry site to ad policy, with the disclosures, consent handling and content limits built in rather than added at the end.
A repeatable section library
Sections such as hero, project overview, tabbed amenities, location with Google Maps embeds, FAQ and enquiry form are built as Elementor HTML widgets with scoped CSS. The same library is reused across multiple launches.
FAQPage schema
FAQ sections carry FAQPage structured data so search engines can read the questions and answers directly.
Compliance details on every page
Each page has the not-the-developer notice, salesperson and agency details, and the unticked consent box as standard parts of the template.
How it works
- Gather the officially released information for the launch, and nothing beyond it.
- Assemble the page from the section library: hero, overview, tabbed amenities, map, FAQ, form.
- Fill in the disclosure notice and salesperson and agency details.
- Add FAQPage schema to the FAQ section.
- Check the page in the Elementor editor and with JavaScript turned off.
- Test on desktop, tablet and mobile before the ads go live.
Decisions and trade-offs
Scoped-CSS HTML widgets instead of standard Elementor widgets. Standard widgets are easy to edit but their styling depends on the theme and global settings, which drift between pages. Writing each section as an HTML widget with styles prefixed to that section means it looks the same wherever it is dropped, and a change to one launch cannot break another. The trade-off is that editors change text in markup rather than in form fields, so I keep the markup simple and clearly labelled.
Content visible without JavaScript. Ad reviewers, crawlers and slow phones all benefit when the core content is in the HTML, not injected by scripts. Tabs and maps enhance the page; they are not required to read it.
Saying less on purpose. It is tempting to add a starting price or "selling fast" to lift conversions. Those claims are exactly what puts ad accounts at risk when they are not officially released. Leaving them out is a deliberate design decision, not an omission.
A library over one-off pages. Building a reusable library took longer at first, but every launch after that starts from tested, compliant sections. My Elementor versus custom theme article explains when this hybrid approach makes sense.
Outcome
The enquiry site was rebuilt to Google Ads policy, and launch pages are now assembled from a repeatable, scoped-CSS section library that has been used across multiple launches. Pages carry FAQPage schema, the required disclosures and an unticked consent box, keep content visible in the editor and without JavaScript, and are tested on desktop, tablet and mobile. I do not publish campaign figures because they are not mine to share.
What I would do next
- Turn the compliance items into a pre-launch checklist that blocks publishing until each one is ticked.
- Add automated layout checks across device sizes.
- Document the section library so another developer could assemble a launch page without guidance.
If you need compliant landing pages, see my WordPress developer service and Elementor developer service, read about the custom widgets in the RENXW theme, or get in touch.
