What a network can already read on this site

A site made only of ad slots is a poor application. Reviewers look for a clear purpose, several pages of your own writing, a way to contact a person, and policies that match the product. Halyard is the public home of a small app studio: three app pages, these guides, and the legal pages stores already ask for.

Already on the site

• Original guides and app pages, written as normal pages rather than keyword blocks.
• About, contact, privacy, terms, cookies, and a disclaimer.
• A layout that fits a phone, which is where your traffic will actually land.
• A consent choice that runs before any advertising script.
• ads.txt at the root of the domain. It has no seller line until you have one to tell the truth about.
• Ad units that stay completely off while the publisher ID is blank. Broken or sample ads are worse than no ads.

Still your job

Approval is not a promise this template can make. Google, and every other network, decides. Before you apply, publish on a domain you control, put an email you read on the contact page, and read the privacy policy as if you were the reviewer. Apply when the pages describe your real apps. If Kept, Settle, and Slate are stand-ins, swap them for the products you actually ship before you file the application.

When an account is approved, the only IDs that should be added are the client ID and slot ID from that account. A publisher ID borrowed from a tutorial, a relative, or another site is a fast way to lose both accounts. The article slot is the only web placement, and it sits in the guide pages, labeled Advertisement.