If you’re building a progressive web app (PWA) for your main website, you’ll need to consider the SEO ramifications.
It’s common to have a dedicated URL to your web app as well as one to your main website. Because most web apps are essentially just single web pages, most of the search engine optimisation techniques that you’d apply to a standard website will also apply to your app.
That being said, there are a few nuances to be aware of so let’s have a brief look at the main ones.
1. Duplicate content
If your web app duplicates content from your main website, you’ll need to specify which you consider to be the authoritative version. This is particularly important if you are using more than one URL. This is done by using a canonical link element in the head of your page.
2. Avoid using hashes (#) in your URL.
Google search bots can’t be relied on to index pages with a hash in the URL so just stick to normal naming conventions and build links based on the path and filenames instead.
3. Ensure everything is accessible
4. Reduce embedded resources
5. Use a sitemap
Sitemaps are still one of the best ways to signal to search bots that you’ve made changes to the structure of your website. Most of the services that generate them are free: see free site map tools. Once you have a sitemap, upload it to Google Search Console. Learn more about sitemaps here: Manage your sitemaps.
6. Ensure you cater for all devices
In order to reach as wide an audience as possible you’ll need to ensure your app is built using responsive design—that way the interface will adapt to whatever screen size your device has. If you’ve done a good job it will work seamlessly on laptops and desktop PCs too.
7. Be fast—Very fast!
Google also emphasises the importance of fast page loading times; in fact, if your page takes too long you’ll rank lower in search results. This is especially important for web apps because they tend to pack a lot of content in on a single page. That means you’ll need to optimise all images, avoid embedding videos, and limit the number of external HTTP requests for resources as possible. You can test your app using Google’s PageSpeed Insights tool.
8. Test updates before you deploy
Building web apps is different to building static web pages. You need to do a lot more testing. Typically, you make an update, test it, then tweak it. It can take many cycles of testing to get it working properly. Make sure it is working correctly before you update the public version. It also pays to test in multiple browsers too. Because web apps use cutting edge web technology features, support can’t always be taken for granted. You’ll need to test using all of the popular browsers: Mozilla Firefox, Google Chrome, Apple’s Safari, and even Microsoft’s new Edge browser.
9. Regular Maintenance
For more reading, we recommend: Building Indexable Progressive Web Apps.