Progressive web app checklist - part 2

Progressive Web Apps (PWA) are reliable, fast, and engaging, although there are many things that can take a PWA from a baseline to exemplary experience.

To help you understand how we create the best possible experiences for your app users we’ve put together this checklist which breaks down all the things it takes to be a Baseline PWA, and how to take that a step further with an Exemplary PWA by providing a more meaningful offline experience, reaching interactive even faster and taking care of many more important details.

Exemplary progressive web app checklist

We perform many of these checks manually, as they are not yet implemented in the compliance tool we use.

Indexability and social

For more information, see these guides to social optimization and social discovery.

1. App’s content is indexed by Google

We check how your app appears to Google when it is crawled.

2. Schema.org metadata is provided where appropriate

We ensure that all recommended metadata, such as title, image, description etc., are supplied, which improves the appearance of your app in search engines.

3. Social metadata is provided where appropriate

We test a representative page of your app in Facebook’s crawler to ensure it looks reasonable. We also ensure that metadata are present to improve your app’s appearance in Twitter.

4. Canonical URLs are provided where necessary

We use canonical URLs to indicate the canonical source of content for each page in your app.

5. Pages use the history API

We use the history API to move backwards and forwards in history. We don’t use fragment identifiers for this purpose.