How to QA a new website or site section
This guide covers minimum checks to complete before and after a new website or site section goes live.
Website QA: before go-live
Once a go-live date has been confirmed, ask content owners to review their pages, forms and menu structure.
Forms
If forms are required, understand privacy requirements before they are built.
To build a new form, use the create a Drupal form and advanced forms guides.
Content owners will need to download and delete submissions as part of data storage requirements.
Content quality assurance (QA)
Complete a final QA of each page to review content and layout. Use the digital accessibility and quality checks guide.
Menus
SDP sites have 2 menus as standard:
main menu (a single menu that displays on the top, side and bottom of a page as the fat footer)
footer menu (menu that displays under the Acknowledgement to Country with required links such as privacy).
Visit the create and edit menus guide.
For breadcrumbs to display on pages, all pages need to be in the main menu. This is important for SEO and UX.
Refer to the site footer - digital guide to see what pages need to be created and added to the footer menu.
Website QA: after go-live
Run a broken link check
After the website is live, it’s best practice to run a broken link check and remediate any broken links.
Add redirects to the CMS
Use the URL redirects to add each redirect to the CMS.
Check functions are working as expected
Test the following are capturing data correctly:
Google Analytics
Was this page helpful
Contact us
Redirects
Website QA: 2 weeks after go-live
Google ranking
Check pages are displaying on first page of Google for main keywords.
Check that search meta data is appearing as expected.
Was this page helpful submissions
Review Was this page helpful feedback and action recommendations where appropriate.
Governance tools
Review governance tools (for example, Hotjar heatmaps) and action any accessibility or policy violations where appropriate.