Checklist for Local Websites

There are 15 steps involved in successfully creating a local site. There are several teams that participate in the process namely, Global content team, Local content team, Developers, Testers, Management, Webmasters, and SEO team. Below is the site-wise break-up of what goes in each step and should not be missed.

Ownership: Development team

Steps:

All plugins and settings will be created at the backend for the local site. This will include the layout of the pages with the blocks and settings that can help in creation of the content and insert them in the already created setup.

Ownership: Automation team (part of wider Group IT team)

Steps:

Automation team has one bot which scans and curates selective data of the legacy website. This can be used to repurpose in the local website, which also includes content, forms, videos, etc.

Onwership: Automation team (part of wider Group IT team)

Steps:

This one is another automatic process wherein all the scrapped content is migrated to the local website and therein it completes most part of the content curation.

Ownership: Global content team

Steps:

Once the above steps are completed, there is sometimes a need to fix few glitches/left-outs/failed records while migrating which is needed to be fixed manually.

Ownership: Global content team

Steps:

For each page there is a need to syndicate pages for the local website. Hence, if you want to showcase a particular page/category, there is a need to check the dropdown for the same.  Before that, please check if the page is approved for syndication.

Ownership: Local content team

Steps:

After the syndication is completed, the Local team is responsible to change the links in the content according to their local website. This is not a mandatory step. In the below case you may replace the Global site link to local website link.

Ownership: Local content team

Steps:

The syndication process will only transfer the web pages from global to local websites, but there can be a need to create webpages according to the local requirements, hence, step allows the Local Content Team to create new local specific pages that can be further added to the local websites.

Ownership: Local content team/Development team

Steps:

You may set up the menus and footer from the backend and the Local Content Team makes sure to change it according to the local requirements.  Under the “Appearance” section, “Menus” option can help you change the name of the menus on the website and also reshuffle the already created ones (if required).

If you need the structure of a particular menu to be copied over, the development team can run a script to run a copy of a menu on the local site, and the local content team can update the links of the menu.

Ownership: Development team

Steps:

While the Development team import database from Global to local website, the Forms also are carried in the database and hence, you will have a complete list of prepared forms. You may check them from the backend, under “Forms” section.

Ownership: Local content team

Steps:

In the pages of research library, client stories where there are maximum chances of having a form, you may modify the forms in the backend as per your page. Check the code of the form and locate the same in the backend. In case you want to know more on how the forms are created and edited, you may take a look at the User guide.

More settings

Ownership: Global content team/Pardot team

Steps:

The team tests the Forms on the webpages so that while the local sites go live the forms are functional. The Pardot team helps the Global Content team with a heads up on submission of Forms. Link to Pardot

Ownership: Local content team and Development team

Steps:

There are two type of pages that are created:

  1. Cookie Policy: It is a list of all cookies used on the website with detailed information about each tracker made available for end users to provide them with insights into how their personal data is being processed when visiting a domain. This is been done by Local content team.
  2. Cookie Settings: Cookie preferences are the types of cookies that users have enabled or disabled on a particular website. This is managed by both Local content team and Development Team

Ownership: Analytics team

Steps:

This allows you to quickly and easily update measurement codes and related code fragments collectively known as tags on your website or mobile app.

Ownership: SEO team

Steps:

Under this the webpage is scanned using a tool for any technical errors and SEO issues that can have negative impact on the search engine checking. It provides a comprehensive list of errors on the webpage that can be used to improve thewebsite.There are three basic tool that are used, SEMRush, Screamingfrog and Google Keyword Planner

Ownership: This is done by local content team with the help of SEO team.

Steps:

Redirects (301 errors) are used to send the site visitors from one URL to another when migrating/replicating from global to local.

Ownership: Team of testers

Steps:

There is a testing server where the replica of the original site is created and all technical details are checked before the site goes live to make sure that everything is in working condition.

Onwership: Global and local content team, local country SPOC

Steps:

Once the testers are sure of the site is smooth, the final go ahead is given by Global Content Team and the Local country SPOC after which the site is send for live by the team of developers. This is the final steps before we can find the site on the platform.