Using Pagefully

Look up any app on the App Store and see three pages planned for it, one drawn on its own screenshots.

Add an app by its App Store name, or by connecting an App Store Connect key.

What Pagefully reads from your App Store listing, what it shows you, and what you approve before pages are planned.

How Pagefully reads your keyword field, what it suggests, and why a page shows for one keyword only.

Follow the apps you are compared with so their listings and reviews shape the pages planned for yours.

Review the pages planned for your app, add one, dismiss a suggestion, and give each page its keywords.

One page for each keyword group and each use case your app serves, in the order of the traffic behind them. The limit is 70.

Build the pages you planned, look each one over as the App Store will show it, and approve the ones you want.

Change a headline, swap a screen, redraw one screenshot, or check every device size before you approve.

Check a page’s other languages before it is sent, and what is and is not translated.

Approve a page on Pages, then send it from Publish. Nothing goes to Apple until you submit it there.

Pagefully puts a page in App Store Connect; you submit it for review there. The steps, and what the statuses mean.

Take back deletes the page from App Store Connect, with its languages. It stays approved in Pagefully, so you can edit and send it again.

Pagefully does not assign keywords yet. Here is how to do it in App Store Connect so the page shows in search.

When your app’s screens change, read the listing again, rebuild the pages that changed, then approve and send them.

What Results shows today, and where to read each page’s views and downloads in the meantime.

The emails Pagefully sends, and how to stop each kind.

Pages, revisions, refreshes, competitors and languages on Free, the Pack and Pro.

Which iPhone and iPad sizes a page is drawn in, and which Apple scales from them.