A brand new business might shell out $3K on a website and think it's getting a bargain. However, when prospective customers start running away in droves because the site is:\r\n<ul>\r\n \t<li>Slow<\/li>\r\n \t<li>Buggy<\/li>\r\n \t<li>Confusing<\/li>\r\n \t<li>Frustrating<\/li>\r\n \t<li>Unsafe<\/li>\r\n \t<li>Broken<\/li>\r\n<\/ul>\r\nWell... It'll quickly prove to be one of those "you get what you paid for"-kind of situations.\r\n\r\nI guess what I'm saying is that if you want a WordPress site for your business or for your clients' businesses that's going to knock visitors socks off and become a conversion generation machine, then a quality assurance plan is a must. And you're not going to get that by rushing through a site or spending very little money or effort on it.\r\n\r\nBy adhering to a strict schedule, referring to rock-solid documentation, and testing your site from every angle, only then can you ensure a top-notch experience for every visitor. This is what a quality assurance plan will do for you.\r\n<h2>Everything a WordPress Quality Assurance Plan Needs<\/h2>\r\nLook, there's absolutely nothing wrong with trying to get a WordPress site built on the cheap. The cost of a really well-done website can be daunting if your business isn't generating revenue yet.\r\n\r\nThat said, there's no excuse that justifies cutting corners once you're on the verge of or even in the middle of your business booming. There's just too much at risk to not have an experienced and talented developer handling your build and a team of QA experts ensuring that all the i's are dotted and t's crossed. Just one too many broken links, too many seconds of wait time, or an outdated or irrelevant photo could send your visitors to the competition.\r\n\r\nIf you want to ensure that your site provides a stellar experience from the very second it launches, then you need to get a solid quality assurance plan in place. Mind you, this is not for the faint of heart. You and your team will need to review the site from every angle--and it's something that should be done mid-development <em>and<\/em> post-development.\r\n\r\nI assure you, though, it's worth it in the end.\r\n\r\nBelow, I have broken out the 25 quality assurance plan tasks your website will need.\r\n\r\n<b>Things to do before you kick off a new web development project:<\/b>\r\n<h3>1. Prepare Yourself<\/h3>\r\nBefore you ever step inside WordPress... Heck, before you even purchase web hosting, have your web development and quality assurance plan all laid out. Whether you're building one website for your enterprise or you're in the business of building dozens of websites for clients every year, you need to know exactly what you intend to do before you go into the project.\r\n\r\nThis will include:\r\n<ul>\r\n \t<li>A set of goals for the website and a rough plan of how you intend on meeting them through design and development.<\/li>\r\n \t<li>A checklist that encompasses every project-related task and its associated deadline. This includes things like storyboarding and wireframing to reduce the chances of discovering issues further on in the QA process.<\/li>\r\n \t<li>A QA step built into every major milestone.<\/li>\r\n \t<li>Clearly defined roles for team members and the tasks they will be responsible for.<\/li>\r\n \t<li>Delegation of QA tasks to the people responsible for vetting work done by others. (No one should be "reviewing" their own work. It's too risky.)<\/li>\r\n \t<li>A schedule that bundles tasks based on involved personnel and task type. Too much jumping around can increase the likelihood that something gets missed.<\/li>\r\n \t<li>Define (and purchase, if needed) the tools you'll be using to manage your project and test the website for quality assurance purposes.<\/li>\r\n<\/ul>\r\nOf course, this action plan needs to be fully documented. Even if you don't intend on developing any other WordPress sites, having a written copy of everything done, every tool used, and every team member responsible for each task will help account for problems that may arise post-launch.\r\n\r\nIn the past, I've used a project management system like <a href="https:\/\/basecamp.com\/" target="_blank" rel="noopener noreferrer">Basecamp<\/a> to create my system of checklists, store my documentation, and templatize the whole thing so it's easy to replicate for future projects.\r\n<h3>2. Purchase Managed WordPress Hosting<\/h3>\r\nManaging your quality assurance plan is going to be a lot of work. To save yourself the trouble caused by using performance-plagued web hosting plans, sign up for <a href="\/blog\/managed-wordpress-hosting\/" target="_blank" rel="noopener noreferrer">Managed WordPress Hosting<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14550" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Pagely-Managed-Hosting.png" alt="Pagely Managed Hosting" width="900" height="385" \/>\r\n\r\nNot only will your site be off to a good start by residing on a fast and secure platform, but you'll have the added benefit of working with WordPress experts who help you maintain speed, security, backups, and manage updates going forward.\r\n<h3>3. Create a WordPress Staging Site<\/h3>\r\nThere are a number of reasons to create and use a WordPress staging site <em>after<\/em> launch. However, you should also be using a staging platform to do the initial build.\r\n\r\nWhy?\r\n\r\nWell, it gives you the freedom and flexibility to develop away from prying eyes. When a website is being built and so much attention paid to quality, disruptions and feedback from key stakeholders <em>not<\/em> involved in development can compromise the plan. So, if you can keep the site away from them until you're ready to show them progress, that would be best.\r\n\r\nIf you have a managed WordPress hosting account with Pagely, you can easily <a href="https:\/\/pagely.com\/blog\/wordpress-staging-site-create\/" target="_blank" rel="noopener noreferrer">create a staging site<\/a> thru them.\r\n<h3>4. Schedule Backups<\/h3>\r\nThere are many ways in which something could go wrong during development: data gets lost, code is accidentally deleted, a bad plugin is installed, etc. With so many people involved in the process, you'll want a scheduled backup system to ensure that a recent copy of your WordPress site is always available. This will make rolling your site back to a safe and vetted version much easier.\r\n\r\nYour web host should be able to help you set up these backups.\r\n<h3>5. Install All Necessary Optimization Plugins<\/h3>\r\nA WordPress website needs to be optimized for speed, security, and search. If you can get those tools in place before any testing takes place, you can ensure that you're QAing the site while it's running at its best.\r\n\r\nThese are the plugins you should install:\r\n<ul>\r\n \t<li>Security<\/li>\r\n \t<li>Caching (focus on the other speed optimization features)<\/li>\r\n \t<li>Image compression<\/li>\r\n \t<li><a href="https:\/\/pagely.com\/blog\/yoast-seo-alternatives\/" target="_blank" rel="noopener noreferrer">SEO<\/a><\/li>\r\n<\/ul>\r\nThere may be other WordPress plugins you need as you go about developing your site, but those can be tackled once you reach those steps.\r\n\r\n<b>Things to do during the development of a WordPress site:<\/b>\r\n<h3>6. Review the Design with End Users<\/h3>\r\nThis is what's known as a cognitive walkthrough. Basically, you want to experience the completed website as an end user.\r\n\r\nFor testing purposes, this is something your WordPress developer should do on their own, something you (or the main stakeholder in the project) should do, your dedicated QA person should take a stab at it, as well as a number of people who've had no hand in the project up until this point. Consider reaching out to clients, employees that work in other departments, or invite random users from the web to test the site out.\r\n\r\nThrough your staging site, you can create temporary login credentials for your users. Other than that, leave them to it. Don't explain what the site is about, what it's selling, or anything else. Just ask them to step into the website and work their way around it.\r\n\r\nHere is what you should be looking for:\r\n<ul>\r\n \t<li>Is it clear what the brand behind the site is and what they do? Will the logo leave a lasting impression? Does the messaging accurately explain the story, goal, and unique selling proposition?<\/li>\r\n \t<li>Are there any issues with the navigation? Was it easy to find? Easy to use? Do the labels clearly explain their intended destination?<\/li>\r\n \t<li>How does search work? Are results relevant? Does it work fast enough?<\/li>\r\n \t<li>Were there any impediments within the design itself that kept users from getting around the site? Colors? Typography? Images? Distractions?<\/li>\r\n \t<li>Did the natural path users take drive them directly to conversion?<\/li>\r\n<\/ul>\r\nIf you're left with more questions and confusion after new users have taken it for a whirl, then you'll need to take this back to the drawing board. Hone in on the specific areas that caused the most friction and iron those out before giving the design another test run.\r\n<h3>7. Test the CTA<\/h3>\r\nThe call-to-action (CTA) will be an essential part of the conversion funnel on your website. While your end users will encounter it during the cognitive walkthrough--and you'll want to get their opinions on it--you need to test this out for yourself as well. Since CTAs are an actual design element that need to be written, formatted, placed, and linked, there is a lot that can go wrong.\r\n\r\nVerify that each CTA:\r\n<ul>\r\n \t<li>Is easy to find.<\/li>\r\n \t<li>Is located in the most logical spot on the page. This is usually right after you've explained the "why", leaving users to want to click the button to find out "how".<\/li>\r\n \t<li>Is styled in a way that complements your branding and design, but also boldly stands out against the rest of the page.<\/li>\r\n \t<li>Is large enough to click on without issue (especially important for mobile).<\/li>\r\n \t<li>Is succinctly and simply worded.<\/li>\r\n \t<li>Links to the page it promised to link to.<\/li>\r\n<\/ul>\r\n<h3>8. Test Contact Forms<\/h3>\r\nEvery contact form on your website needs to be tested. It doesn't matter if the form is identical from page-to-page. If there is a new instance of it, you need to verify that it works as promised.\r\n\r\nCheck your forms for the following:\r\n<ul>\r\n \t<li><b>Placement on the page.<\/b> Like the CTA, it should appear in a location where it's expected.<\/li>\r\n \t<li><b>Wording.<\/b> This pertains to any directions given above the form as well as labels placed inside and outside of the fields. Do they make sense?<\/li>\r\n \t<li><b>Size of the fields.<\/b> This might not be a big deal for the average user, but for mobile as well as accessibility-impaired users it will.<\/li>\r\n \t<li><b>Steps.<\/b> Some contact forms are more complex than others, so only include the number of fields and steps that are necessary.<\/li>\r\n \t<li><b>Button.<\/b> The CTA of a contact form needs to be reviewed the same as all other buttons on the site.<\/li>\r\n \t<li><b>Confirmation.<\/b> There are three kinds of confirmations to verify: 1) Did the end user receive a confirmation message on screen or be directed to a thank you page?, 2) Did the end user receive a complementary confirmation email?, 3) Did the admin of your site receive a confirmation email regarding the form submission? And did the messages make sense?<\/li>\r\n<\/ul>\r\nBe sure to do this for all contact forms, even for ones with a single field for people to subscribe to your newsletter or blog.\r\n<h3>9. Test Checkout<\/h3>\r\nThe same process needs to happen if your website has an e-commerce checkout. The testing process for the contact form and confirmation will be the same as with a standard contact form. What will differ, however, is the following:\r\n<ul>\r\n \t<li>Testing the login, if you allow users to sign in with a saved account, social media, or Amazon.<\/li>\r\n \t<li>Testing the payment gateway to ensure that it captures the right details and completes the transaction.<\/li>\r\n \t<li>Confirming the purchase was registered on your end and that the delivery of the product, subscription, or service was initiated.<\/li>\r\n<\/ul>\r\n<h3>10. Force Errors to Occur<\/h3>\r\nObviously, the whole reason you have a quality assurance plan is to prevent errors from occurring. That said, it's inevitable. A link might break without you knowing. A user may try to go to an old page that doesn't exist anymore. Or a contact form could be filled out improperly.\r\n\r\nTake each of these potential scenarios into consideration and force them to happen during your QA phase.\r\n\r\n<img class="aligncenter size-full wp-image-14551" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Forced-Error.png" alt="Forced Error" width="900" height="889" \/>\r\n\r\nWith an incomplete or incorrectly filled out form, verify that the error message indeed shows up. Also, make sure that it's clear why there was an error. Did someone miss a required field? Was the right kind of text inputted? Is there something else wrong with the form?\r\n\r\nWith a bad URL request, review how that looks to the end user. Is any sensitive database information exposed in the error message (which can happen)? Is the resulting message too cold or unclear? You may want to give users testing the design a look at the error message. They might be more comfortable if you instead redirected them back to the home page.\r\n<h3>11. Play Around with Interactive Elements<\/h3>\r\nAny interactive elements you've included on your site will need a thorough QA round, too. These could be things like:\r\n<ul>\r\n \t<li>Pop-ups<\/li>\r\n \t<li>Calculators<\/li>\r\n \t<li>Image galleries<\/li>\r\n \t<li>Video or audio players<\/li>\r\n \t<li>Downloadable content<\/li>\r\n \t<li>Live chat<\/li>\r\n \t<li>Social media links or shares<\/li>\r\n<\/ul>\r\nLook at how they show up on the page, review the design, read the wording, and make sure they're only triggered to show up or animate when and where they're supposed to. And don't forget to review them on mobile. For many of these interactive elements, they'll be too overwhelming on mobile and you'll want to remove them entirely from that experience.\r\n<h3>12. Read through the Copy<\/h3>\r\nThis QA task is best left up to your site's proofreader and editor. Ideally, this will be done before any copy is put into WordPress.\r\n\r\nThe proofreader can start by using a spelling and grammar checking tool like <a href="https:\/\/www.grammarly.com\/" target="_blank" rel="noopener noreferrer">Grammarly<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14552" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Grammarly.png" alt="Grammarly" width="900" height="499" \/>\r\n\r\nEach page can be popped in here and the proofreader can run a check to quickly take care of glaring errors. This'll reduce the amount of time spent on cleaning up the rest.\r\n\r\nThe editor will then need to read through each page carefully to ensure it's been written to align with the site's original goal, that it stays on topic, and the language is strong and clear.\r\n\r\n<a href="http:\/\/www.hemingwayapp.com\/" target="_blank" rel="noopener noreferrer">The Hemingway Editor<\/a> is a tool I'd suggest editors use to clean up clunky language and ensure the text is readable.\r\n\r\n<img class="aligncenter size-full wp-image-14553" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Hemingway-Editor.png" alt="Hemingway Editor" width="900" height="493" \/>\r\n\r\nOf course, the editor should be well-versed in proper structuring and formatting of text, too. Your pages need to be scannable with bold and well-written headers, bulleted sections, and good spacing.\r\n<h3>13. Confirm with the SEO Plugin<\/h3>\r\nOnce you've let your people read through and edit the content, it's time to test it in WordPress. The plugin I prefer to use for this is <a href="https:\/\/wordpress.org\/plugins\/wordpress-seo\/" target="_blank" rel="noopener noreferrer">Yoast SEO<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14554" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Yoast-Scores.png" alt="Yoast Scores" width="900" height="457" \/>\r\n\r\nIt provides me with instant and clear feedback about:\r\n<ul>\r\n \t<li>The readability of my pages.<\/li>\r\n \t<li>My SEO optimization score.<\/li>\r\n \t<li>The number of internal links the page has.<\/li>\r\n \t<li>The number of external links that point to the page.<\/li>\r\n \t<li>What I can do to improve the SEO friendliness of the page.<\/li>\r\n<\/ul>\r\n<img class="aligncenter size-full wp-image-14555" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Yoast-Analysis.png" alt="Yoast Analysis" width="900" height="760" \/>\r\n\r\nKeep in mind that these are just the basics of SEO; that is, writing good copy and optimizing it around a keyword. There's much more to SEO than that, so make sure you follow <a href="https:\/\/pagely.com\/blog\/2018-seo-checklist-webmasters\/" target="_blank" rel="noopener noreferrer">your SEO checklist<\/a> before launching a new site.\r\n<h3>14. Test Every Link<\/h3>\r\nI know this one is a pain, but it needs to be done as broken links can get annoying real fast if visitors are excited about your site, but continue to encounter dead ends.\r\n\r\nFirst, install the <a href="https:\/\/wordpress.org\/plugins\/wp-link-status\/" target="_blank" rel="noopener noreferrer">WP Broken Link Status Checker plugin<\/a>. Once all your content is in place, run a scan on the links to uncover any that are broken. If you find any, repair them. Then, when you're done, delete the plugin from WordPress. You don't want it draining resources while your site is live.\r\n\r\nNext, <a href="https:\/\/pagely.com\/blog\/wordpress-redirects\/" target="_blank" rel="noopener noreferrer">set up a system of 301 redirects<\/a> to handle any future broken links. This will help keep users on your site and away from the dreaded 404 error page.\r\n\r\nFinally, you're going to need to do a sweep of all anchor text used in your links. The best person to assign this to is the editor or SEO as they'll be familiar with the kinds of keywords internal links should be connected to.\r\n<h3>15. Look Over Your Images<\/h3>\r\nBy now, you already have an <a href="https:\/\/wordpress.org\/plugins\/wp-smushit\/" target="_blank" rel="noopener noreferrer">image optimization plugin like Smush<\/a> in place. This will take some of the work out of making images lean and mean.\r\n\r\nWhat you need to do now is verify that:\r\n<ul>\r\n \t<li>Images appear when they're supposed to.<\/li>\r\n \t<li>Placement on the page makes sense.<\/li>\r\n \t<li>Alt tags are used for users with accessibility issues.<\/li>\r\n \t<li>Images are consistently sized around the website when they appear in the same location or for the same function.<\/li>\r\n \t<li>Every image appears crystal-clear.<\/li>\r\n \t<li>The colors within the image don't conflict with the rest of the page.<\/li>\r\n \t<li>The content of the image is relevant to the message of the page.<\/li>\r\n \t<li>Any text displayed on top of the image can be easily read, even if scrolling over a parallax image.<\/li>\r\n \t<li>Any captions provided for images correctly match them.<\/li>\r\n<\/ul>\r\n<h3>16. Check for Coding Compliance<\/h3>\r\nEven if you only have one WordPress developer building your site, or you've relied heavily on a theme and plugins to build it, you should still check the quality of the coding for issues. You can do this with <a href="https:\/\/validator.w3.org\/" target="_blank" rel="noopener noreferrer">W3's Validator tool<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14556" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/W3-Validator.png" alt="W3 Validator" width="900" height="215" \/>\r\n\r\nIt will reveal any issues detected with your HTML and give you a chance to clean those up before you push your site live. In the end, that'll help your site run more efficiently.\r\n<h3>17. Check for Accessibility Issues<\/h3>\r\nAccessibility, in general, is a pretty complex matter, so I won't cover all the points you need to focus on here. However, I do want to stress how important it is for your site to cater to impaired individuals now that <a href="https:\/\/www.forbes.com\/sites\/legalnewsline\/2017\/10\/02\/lawyers-awarded-100k-after-historic-verdict-for-blind-internet-users-winn-dixie-appealing\/" target="_blank" rel="noopener noreferrer">websites are being held legally liable<\/a> for accessibility issues.\r\n\r\n<img class="aligncenter size-full wp-image-14557" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/WCAG-Guidelines.png" alt="WCAG Guidelines" width="900" height="420" \/>\r\n\r\nThe WAI keeps a set of <a href="https:\/\/www.w3.org\/WAI\/WCAG20\/quickref\/" target="_blank" rel="noopener noreferrer">Web Content Accessibility Guidelines<\/a> updated on its website at all times, so I would suggest using that as your accessibility checklist.\r\n\r\n<b>Things to check once during development and again after the launch of your WordPress site: <\/b>\r\n<h3>18. Test Browser and Device Compatibility<\/h3>\r\n<a href="https:\/\/pagely.com\/blog\/optimize-wordpress-mobile\/" target="_blank" rel="noopener noreferrer">Mobile-first indexing is here<\/a>, so this quality assurance test is not optional.\r\n\r\nThere are four tools and methods you will need to use to test your website's cross-browser and device compatibility.\r\n\r\nThe first is to review each page of your site within WordPress.\r\n\r\n<img class="aligncenter size-full wp-image-14558" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Customize-Device-Controls.png" alt="Customize Device Controls" width="900" height="406" \/>\r\n\r\nIf you want to check the whole site at once, you can do this by opening your Appearance menu and navigating to Customize. This will take you to your theme's settings. In the bottom-left corner, you can select the generic device size and then scan through how your website looks on the right. It won't be exact, but it's a good place to start.\r\n\r\nIf you're <a href="https:\/\/pagely.com\/blog\/wordpress-page-builders\/" target="_blank" rel="noopener noreferrer">using a page builder tool<\/a> or a theme with a visual builder, you can review your on-page compatibility with tablets or mobile devices when developing in real-time, too.\r\n\r\nNext, you'll need an app like <a href="https:\/\/www.browserstack.com\/" target="_blank" rel="noopener noreferrer">Browser Stack<\/a> to test your website on all major devices and browsers.\r\n\r\n<img class="aligncenter size-full wp-image-14559" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Browser-Stack.png" alt="Browser Stack" width="900" height="350" \/>\r\n\r\nLike WordPress, tools like these have their limitations. Use what you learn here as a reference point, but not as the final say on your site's responsiveness.\r\n\r\nNext, test your site's cross-browser compatibility manually. I know, I know... It sucks. But it's the only way to know for sure that everything looks good <em>and<\/em> works as it's supposed to on smaller screens.\r\n\r\nAnd, finally, once your site is live, run it through <a href="https:\/\/search.google.com\/test\/mobile-friendly" target="_blank" rel="noopener noreferrer">Google's Mobile-Friendly Test<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14560" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Google-Mobile-Friendly.png" alt="Google Mobile-Friendly" width="900" height="387" \/>\r\n\r\nGoogle will give you the all-clear and may also give you tips on how to fix rendering issues.\r\n<h3>19. Test for Speed<\/h3>\r\nThere are a number of free online speed testing tools you can use, but I prefer <a href="https:\/\/developers.google.com\/speed\/pagespeed\/insights\/" target="_blank" rel="noopener noreferrer">Google's PageSpeed Insights<\/a>.\r\n\r\n<img class="aligncenter size-full wp-image-14561" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Google-PageSpeed.png" alt="Google PageSpeed" width="900" height="578" \/>\r\n\r\nI like that Google not only provides me with a speed score for both the desktop and mobile experience, but it also provides me with tips on how to fix issues with coding or images that are impacting performance.\r\n<h3>20. Test for Stress<\/h3>\r\nWhile speed testing is good to get a sense of what your WordPress site's baseline is, it won't tell you what will happen in the case of a traffic spike. When your site and server are put under a lot of stress, you need to ensure that your resources are capable of handling it.\r\n\r\nRather than seek out stress-testing tools on your own, though, work directly with your web hosting company on this one. Pagely recommends that its customers use <a href="https:\/\/loadimpact.com\/" target="_blank" rel="noopener noreferrer">LoadImpact<\/a> to run their tests but to work in conjunction with Pagely to <a href="https:\/\/pagely.com\/kb\/kb\/what-sort-of-performance-monitoring-and-alerting-do-we-have-access-to\/">monitor performance<\/a>.\r\n<h3>21. Test for Security<\/h3>\r\nSecurity is a major concern for every website owner. Once you have all security measures in place at the WordPress and server levels, you need to be able to put them to the test.\r\n\r\n<a href="https:\/\/sitecheck.sucuri.net\/" target="_blank" rel="noopener noreferrer">Sucuri SiteCheck<\/a> is the tool I prefer to use for this.\r\n\r\n<img class="aligncenter size-full wp-image-14562" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Sucuri-SiteCheck.png" alt="Sucuri SiteCheck" width="900" height="418" \/>\r\n\r\nIt lets me know if there's any malware or spam detected, if any of my WordPress software is out of date, if there are issues with the firewall, or if (gulp) my site has been blacklisted in search. You can also use your WordPress plugin to run a scan and check for vulnerabilities.\r\n<h3>22. Test Google Analytics<\/h3>\r\n<a href="https:\/\/analytics.google.com\/analytics\/web\/" target="_blank" rel="noopener noreferrer">Google Analytics<\/a> is a critical piece of every WordPress site. Without this tool, it'll be near impossible to make any type of well-informed strategic decisions for your website in the future.\r\n\r\nTo start, confirm that it's been added to your site. The easiest way to do this is to log into your Analytics account and make sure there's traffic coming in.\r\n\r\nNext, configure any additional modules you need to track for. Like Ecommerce. Google Analytics can be a really powerful tool if you configure it to pull in the right data.\r\n\r\nAlso, enable Goals for your site. This way, if visitors aren't following the right sales funnel, if sales are slow, if any other milestones aren't being hit, Google Analytics can let you know.\r\n<h3>23. Verify Your Site Is Being Indexed<\/h3>\r\nOnce your site has been live for about a week, go to Google and search for your domain name. While a week is way too soon for your site to be indexed <em>and<\/em> ranking on the first page, a direct search for your website will let you know if there are any problems in general with indexing.\r\n\r\nIn the meantime, you can use <a href="https:\/\/www.google.com\/webmasters\/tools\/" target="_blank" rel="noopener noreferrer">Google's Search Console<\/a> to verify that your entire website has been indexed.\r\n\r\n<img class="aligncenter size-full wp-image-14563" src="https:\/\/pagely.com\/wp-content\/uploads\/2018\/05\/Google-Search-Console-Indexing.png" alt="Google Search Console Indexing" width="900" height="404" \/>\r\n\r\nIf you discover any issues, check these two files from your website:\r\n<ol>\r\n \t<li>robots.txt - which will tell search engines whether or not to index your site or certain pages within it<\/li>\r\n \t<li>sitemap_index.xml - which will provide search engines with all the indexable pages on your site<\/li>\r\n<\/ol>\r\nIf either of these are missing or contain erroneous information, fix them and resubmit your site to Google. If you're using an SEO plugin, it can do that for you. If not, just do it through the Google Search Console.\r\n<h3>24. Test Third-Party Integrations<\/h3>\r\nWith your website live, you'll need to test your third-party integrations the way you tested your on-site contact forms. So, if you've connected WordPress to any of the following, test out those processes to ensure they do what was intended.\r\n<ul>\r\n \t<li>Email marketing<\/li>\r\n \t<li>CRM lead generation<\/li>\r\n \t<li>Landing page campaigns<\/li>\r\n<\/ul>\r\nIt would be a shame to give an app access to your site, only to find out they weren't working right, so keep this in mind any time you add a new tool to your site.\r\n<h3>25. Amend Your Quality Assurance Plan on an Ongoing Basis<\/h3>\r\nWhat I've given you here is a list of the basic elements a WordPress quality assurance plan should contain. However, that doesn't mean you can't or shouldn't take this and make it your own. If you develop websites for a particular industry and find that there are other elements that need testing (like reservation systems, product pages, push notifications, etc.), add them to this checklist.\r\n<h2>Wrapping Up<\/h2>\r\nWith so much at stake when a user's experience is disrupted, you can't afford to leave your WordPress site without a comprehensive quality assurance plan. The 25 tools, tips, and tests above will get you started. But also be sure to sign on with <a href="https:\/\/pagely.com\/" target="_blank" rel="noopener noreferrer">a managed WordPress hosting provider like Pagely<\/a> to help you address the security, performance, and backup piece of the puzzle.