Check the supported destination and campaign goal before assuming Google Ads can run without a website. An eligible app-store destination belongs to a documented app-promotion workflow; it does not establish that any ordinary business can advertise using any link. If the intended action needs a web page, prepare that page and its measurement before campaign setup.
Separate three questions: what the person will do, where the advertisement will take them and how the outcome will be observed. A business can have a useful online presence without every part of that presence being an acceptable destination for a chosen advertising format. Start with the exact route rather than a blanket yes or no.
Which no-website route is actually documented?
Google documents App campaigns for installs, engagement and pre-registration. The App campaign overview lists a published Google Play or Apple App Store app among its starting requirements. Read these statements within the App campaign documentation, then follow the requirements for the particular subtype being considered. A business without an app cannot use the existence of this route as evidence that its unrelated service advertisement needs no website.
The App campaign overview requires a valid payment method linked to the account. App campaigns can use assets from the app’s store listing. The preparation brief should therefore identify the actual app, the responsible publisher and the intended app action. “We have an app idea” is a different readiness state from a store listing that supports the selected workflow.
A Business Profile listing and an independently hosted website are different assets. Google’s Business Profile editing guide asks for a full URL when entering a business website. The current profile guidance describes a website field, rather than establishing approval for an advertising destination. Record the URL and inspect where it leads instead of assuming that the profile supplies the landing page needed by the chosen campaign.
For a business that primarily needs enquiries, describe the enquiry journey first. Determine the campaign’s current supported requirements in the account before promising a website-free setup. A telephone number or a social profile appearing somewhere in an interface does not by itself settle the destination and conversion requirements of the proposed campaign.
What destination rules still need to be checked?
Google requires advertising destinations to work on common browsers and devices. Advertising destinations must be accessible in the targeted location. These requirements in the destination policy apply to the actual experience, so a link that works only for the business owner is inadequate evidence for campaign preparation.
The destination requirements prohibit a mismatch between the advertised destination and the app or website reached. Google requires the destination and its content to be crawlable by AdsBot. Inspect redirects and access restrictions as part of the destination review. A visually convincing page may still fail a different part of the requirements.
The destination experience policy disallows ad links that lead directly to an email address or file. Do not propose an email link or a brochure PDF as a universal replacement for a landing page. Give the reader an accessible, useful route that suits the chosen format and task, with clear information before the action.
App and web-store destinations must follow their respective store policies. An app-store destination therefore introduces its own review work rather than removing the need for a destination review. Confirm the listing, the promised action and the relevant store requirements together.
| Proposed route | What to establish first | What it does not establish |
|---|---|---|
| App-store destination | Actual app and supported campaign subtype | Permission for an unrelated service ad |
| Independently hosted landing page | Useful content, working route and measurement | Acceptance merely because the URL loads |
| Business Profile | Correct business information and supported use | A universally valid advertising destination |
| Telephone-led enquiry | Current format requirements and observation method | That every call-related feature is available everywhere |
| Email or document link | A suitable alternative information journey | A universal valid final destination |
How do conversion limits affect the choice?
Define the outcome in terms the business can verify. An app installation, a completed in-app action, a connected enquiry and a submitted website form are different events. Do not reuse one measurement label across them simply because all are desirable.
Write down where the evidence comes from and who can inspect it. If the chosen route does not provide the required observation, change the measurement plan or choose a more suitable destination. Avoid treating absence of a website as permission to count every interaction as a completed sale.
The conversion tracking guide covers event design and test evidence. Use it after choosing the actual destination and goal. A measurement plan built around a form cannot be accepted unchanged when the campaign instead sends people to an app store.
Original destination-route decision card
Use this hypothetical exercise for two businesses considering advertising: a booking-app publisher and a small training provider with only a social profile. The original decision card records goal, destination, supported route, measurement evidence and unresolved prerequisite for each proposed campaign.
App publisher card. The goal is to encourage a defined app action. Enter the app’s store listing and the selected App campaign subtype. Have the publisher verify that the listing describes the same service as the creative. Then ask the measurement owner to describe how the selected action will be observed. Keep a missing measurement connection as a prerequisite rather than quietly changing the goal to something easier to count.
Training provider card. The goal is a course enquiry, but the business has no independently hosted page. Write down the information a prospective attendee needs: course purpose, audience, format, dates if agreed and a clear enquiry action. Assess the actual campaign’s supported route against that information need. If the proposed route cannot deliver it, a focused landing page is a concrete requirement to resolve.
Saved destination card. An old briefing document points to a previous campaign destination. Open it on the intended devices, identify the asset it currently serves and check it against the chosen campaign’s requirements. Confirm the business controls any replacement before updating the brief.
Acceptance row. For each card, name the reviewer and retain a device check, redirect check and outcome observation plan. Record ready for account review, destination work required or campaign route unresolved. This turns an abstract argument about needing a website into a precise list of the remaining work.
What should a business prepare next?
Prepare a concise destination brief with the exact goal, proposed link, content owner and observation method. Include any app-store or account prerequisite that still needs confirmation. This gives the person configuring the account a reviewable proposal rather than a request to discover the entire customer journey during setup.
For a website route, see web design and Google Ads planning. To discuss the destination decision, get started with the completed route card and the information a customer needs before taking action.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.