[rev_slider alias=”blog”][/rev_slider]

On January 3, 2019 Adlava, a web design company based in Las Vegas, collectively decided to launch a new website in Webflow CMS. We’d used WordPress for all previous iterations of our website, and I was tasked with making sure the transition went smoothly from an SEO standpoint.

Having never used Webflow CMS before, I decided to make a list of all the major on-site SEO elements I knew I‘d need access to, and researched how to implement them with Webflow CMS. I tracked our progress during this process, and here’s what happened after a month:

Organic search traffic increased

Since we’re focusing on SEO, I dug into our website’s Google Analytics reports for organic search to exclude any ads, campaigns, or social media posts promoting the launch of the new website.

Seasonality aside, organic search traffic is a useful key performance indicator (KPI) for SEO because it not only gives you an idea of how many users find you through search, but also whether those users found your website useful.

In other words, it helps you determine whether you’re reaching the right people.

‍

Overall, performance increased virtually across the board. Our bounce rate in particular saw a 20% decrease after the launch of the new website. This metric matters because it tells us whether visitors are able to find what they’re looking for when they visit our website.

Since we’re a primarily B2B professional service, we see much more desktop traffic than the general population, but when we segment our Organic Search traffic by device type, we see improvements in Bounce Rate for both mobile and desktop.

‍

Our website ranked for 30% more organic keywords

Some particularly volatile Google updates around October of 2018, combined with a shift in our business services and keyword targeting, caused a bit of fluctuation in our domain’s keyword ranking (making it that much more important for us to focus on SEO on our new website).

At our lowest point, our website ranked for 406 Organic Keywords (as reported in ahrefs). By the end of our first month after launch, our website ranked for 528 organic keywords — an increase of 122 keywords, or 30%.

How are the major SEO elements handled in Webflow?

After going through the redesign and migration process, I noticed a few minor differences when implementing some of the major onsite SEO elements in Webflow. Fortunately, I took note of these details so you don’t have to! This is by no means a complete checklist, but it can help point you in the right direction.

1. Meta titles and descriptions

There’s not a huge difference between Webflow and most other major CMSs on the meta title and description front, but one important thing for designers to note is that you must add the fields and tie the corresponding options to the fields, otherwise they won’t show up in the source code, even if they’re filled out.

This is especially important if an editor will be adding the titles and descriptions rather than the designer.

2. Open Graph settings

For those who neglect their Open Graph settings, or allow WordPress to pick an image, make sure you specify images, titles, and descriptions in Webflow (or select the setting to match your SEO settings).

This is especially important on blogs, where WordPress normally uses the “Featured Image” if there is no Open Graph image specified. If you don’t specify an image in Webflow, your website won’t display a preview image when sharing to social media.

3. 301 redirects

No matter which CMS you use, there will likely be pages that change and/or go away when you redesign a website. To prevent users from landing on broken pages (and to minimize loss of backlink equity) remember to crawl your existing website and set up 301 redirects appropriately. This is handled natively in Webflow, and while there’s no CSV upload option, you can use rules to redirect groups of URLs sharing similar formats.

4. Robots.txt and sitemaps

Robots.txt and XML sitemaps are both handled natively in the Webflow CMS. Webflow University provides excellent resources for both, but the important thing to remember is that you don’t want your subdomain or development website crawled by search engines. Use your robots.txt to block or allow crawlers accordingly, and submit your XML sitemap as usual in Google Search Console.

5. Google Analytics and Google Tag Manager

As a personal advocate for Google Tag Manager, I would strongly recommend going the Tag Manager route and integrating your Google Analytics with Google Tag Manager. Webflow University provides detailed instructions on how to do this. If you opt to go the Google Analytics route, Webflow has a designated spot to simply plug in your Property ID.

6. Google and Bing verification

Pay special attention to your Google site verification if you normally verify by Google Analytics or Google Tag Manager detection.

As mentioned in the Webflow University links in the previous point, Google Tag Manager can be added to the custom code head and footer sections. While this will work to deploy Google Tag Manager, Google Search Console was not able to recognize the scripts when we used this method for site verification.

When migrating your website, you should use Webflow’s designated spot for the HTML tag method to keep your verification status in Google Search Console — even if you have Google Analytics and/or Google Tag Manager on your website. There is no designated spot for Bing Webmaster Tools verification, but we were able to verify the website by adding the HTML tag to the custom code section in the head. You could also avoid this by using the DNS option to verify your website instead.

7. Image alt text

If you manage websites where ADA compliance is a priority, or if you simply value accessibility, you’re probably familiar with the common alt text issues that come with WordPress. Specifically, the issue of image alt text not showing in the source code after adding it in the media library. Fortunately, we found alt tagging our images to be much more straightforward on Webflow.

Good user experience is good SEO

One of the main reasons Adlava decided to move to Webflow CMS was that it gave us more design flexibility and allowed us to implement website changes much quicker and more efficiently.

Hearkening back to the SEO basics, good user experience is good SEO. Remember that Google’s ultimate goal is to serve results that are useful to users when they perform a Google search. If you’re sacrificing user experience for a specific technical element, that’s not good SEO. The end goal is to create useful web content. The above tips should help you navigate the technical implementation side of things — the quality content is up to you.