L1 – CRITICAL
L1 – PROGRAMMERS
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Forms:1. Javascript validation for mandatory fields.2. Tab order.3. Standard Alert messages.4. Captcha (shape match) functionality/validation and refresh button (in case of multiple forms make sure that there is no verification code mismatch issues).5. Hourglass function on form submission and Kill submission button once it has been clicked to avoid duplicate send/conversion.6. Confirmation message/Thank You page (ensure recording conversion in AdLuge – see SI # 7 and 8).7. Autoresponder mail and template as per form fields.8. Admin notification mail as per form fields and TW standard. 9. ADLUGE lead tracking.10. Make sure that all user section pages have visitor tracker.js file included.11. Ensure spam filter is implemented (when insisted by the client.)12. Ensure that the given all codes are present in respective pages. |
| 2. | Canonical redirection:Check redirections from non-www to http://www eg: ‘http://example.com’ to ‘http://www.example.com’. Also, ‘http://example.com/index.php’ to ‘http://www.example.com’. This needs to be done in .htaccess file. |
| 3. | Check for dynamic broken links (URLs). Recommended using XENU. |
| 4. | Make sure that there is no wysework or techint path in the live site and ensure all test data is removed from the site & ADLUGE, including “Hello World” blog entry |
| 5. | The .htaccess should have code to redirect to 404 for broken links |
| 6 | Check availability of GA Code in all the pages (Ensure it is placed above closing head tag) |
| 7. | Check for AdWords conversion code in thank-you page in case of PPC clients. Also ensure that conversion code is not present in any other pages than Thank You page |
| 8. | If using WordPress, in privacy settings make sure that the search engines should be crawlable. |
| 9. | Ensure that phone tracking script is implemented properly.1. Script presence in all pages.2. Phone number is text.3. Number change on refresh.Cross check the tracking code with one in AdLuge. Also check whether the respected Phone tracking in the site is enabled in the AdLuge API settings. |
| 10. | Ensure that content is updated in the website as per ticket notes |
| 11. | 301 redirection should be done in case of URL change.(Requirement should be conveyed to SEO team and as per the doc provided by SEO team the changes should be done) |
| 12 | Check for 404 pages in case of URL change. |
| 13. | While testing a form — In Comments field the test data entered should be ‘Test mail from TechWyse. Please disregard’. All required field entry should track in AdLuge. |
| 14. | Ensure that test leads are in Spam folder in AdLuge. |
| 15 | Dummy text and test images should be removed from the admin(media gallery) and user side |
| 16 | Make sure that Fax number is not changing when call tracking is implemented. Only phone number should be change. |
| 17. | Ensure that requirements in ticket are done perfectly. |
| 18. | Ensure that client Email id is added back in admin after testing forms. |
| 19. | During Setup phase the Website Account type in Manage Websites in AdLuge should be ‘Setup’ |
| 20. | Ensure V4 Tracking script is placed properly in Websites. |
| 21 | Check POD and requirement docs attached in the ticket. |
| 22. | Ensure that Spam checking code is implemented in Phone number field in forms |
| 23 | FTP list should be updated when the project is launched. |
| 24 | Site Speed – Should verify the Minimum server requirements, optimization code, iphone.htaccess. |
| 25. | Ensure that Server Side Validation is done in the forms. |
| 26 | Ensure to run xenu after a new change is done in the module. |
| 27 | Double ensure the client names because same client name can be given to multiple clients |
| 28 | Make sure the given FTP Details should be updated on the Keeper logins.And make sure that the updated screenshot is attached by priyanka in the WorkRequest |
| 29. | Whenever a website goes from Setup to Recurring, QA must make assure that lead alert must be enabled for at least one end user. |
| 30 | Ensure the plugins and WordPress are in the latest version during the pre-launch checking. |
| 31 | Make sure the security plugin “Wordfence” should be active during the WyseWork launch of the site. |
| 32 | Ensure that landing page URLs function properly whether accessed with or without /? at the end. |
WP- Security L1 – PROGRAMMERS
| 1. | DB Password should be strong |
| 2. | While adding new users, role should be set as ‘Subscriber’ by default |
| 3. | Unwanted themes should be deleted |
| 4. | Securing wp-includes and wp-config (Need to send a screenshot by the programmer) |
| 5. | Disable File Editing (Need to send a screenshot by the programmer) |
| 6. | WordPress admin logins — Username should not be admin and Password should not be an easy one |
| 7. | Site should be blocked in robots.txt in Wysework. User-agent: *Disallow: / |
| 8. | Make sure that the direct listing is disabled in HTaccess. |
| 9 | Moving forward, We have advised to keep a list of active plugins before WP update and match it once WP is updated as well. They will also be keeping a list of custom modules developed as well for each of the clients and this will be noted in each of WP update tickets. |
| 10 | Ensure the team does not disable any plugin without the confirmation of the CAN team, especially security,SEO, Cache plugins. For checking purposes,if we need to disable any plugin, we will get it with the Approval of CAN team. In case of WP upgrade, before and after Plugin page screenshots will be added . |
| 11 | Made sure the team won’t reset FTP/Admin Password or create a new FTP account without the confirmation from the CAN team. Also the team won’t create an additional admin account even if we have CPanel access. |
| 12 | Team should correctly update the request note regarding the plugins. |
| 13 | In the admin side, “Search Engine Visibility” should be checked when the site is in WyseWork and unchecked when the site is made to Live. |
| 14 | If there is any request to set ‘no follow, no index’ only to the suggested pages in the audit, Should ensure the pages randomly to make sure the changes do not affect any other pages of the site other than in the mentioned pages. |
| 15. | Reset Password or Logins Not Working:The team will update the note “logins updated in 1Password” in the request and pass it to QA. |
| 16. | Password Update Request through Email/Chat:The respective PM or TL should create a new request, add a note, and pass it to QA. |
| 17. | Account Login Issues:If there are any account login issues, separate requests should be created by the respective TL or PM to address them. |
| 18. | A monthly check should be conducted for all the staging sites to ensure that the sites are not indexed in Google. |
| Auto-updated plugins should be off |
L1 – Designers
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Broken design(Creative & Development):-Alignment issueImage BrokenHomepage bannersInner page bannersSide bannerForm alignment Footer |
| 2. | Broken Links(Development). All links should be pointed to relevant pagesEmail template banner link / footer link should point to the home page of the site.Recommend xenu and w3c validator to verify the links, HTML and CSS |
| 3. | Custom 404 Error page with a link to the site map(Development) |
| 4. | Thank you Page should have a Back button that redirect to the form submitted page (using JavaScript)(Development) |
| 5. | TechWyse stamp applied to the footer in all the pages?(Creative & Development) |
| 6. | Content(Creative & Development):-Spelling mistake in banner, footer, titles and navigation.Banner and email template phone numbers.Put the standard ‘Coming Soon!’ if content is not provided. Also Please ensure whether the font size of the title, subtitle are consistent. |
| 7. | Check for availability of ‘title/alt’ attribute in header menu links, logo, image and all buttons(Development) |
| 8. | Ensure that content is updated in the website as per ticket notes(Creative & Development) |
| 9. | Bottom navigation should follow our standard ie bottom navigation should be at the footer and centred(Creative & Development) |
| 10. | All client images for social networks should be made in .PNG |
| 11. | While testing a form — In Comments field the test data entered should be ‘Test mail from TechWyse. Please disregard’(Development) |
| 12 | Dummy text and test images should be removed from the admin(media gallery) and user side(Development) |
| 13 | Landing page: When banner is updated in landing page same should be implemented in Thank You page too. (Includes Phone number, changes in footer etc)(Development). |
| 14 | Blog posts should not say ‘Posted by Admin’(Creative & Development) |
| 15 | Ensure that test leads are in the Spam folder in AdLuge(Development). |
| 16 | Ensure that ‘Read More’ tags are implemented for Blogs in Blog page(Creative & Development). |
| 17 | Ensure that requirements in ticket are done perfectly(Creative & Development). |
| 18 | Logo of a website should be in .PNG(Development) |
| 19 | Shutterstock watermark should be removed(Creative & Development) |
| 20 | In case of responsive design ensure that design is not broken in iPad and iPhone(Development) |
| 21 | In the case of responsive design ensure the main banner image resizes on mobile and tablets(Development) |
| 22 | Top menu should remain static while scrolling down(Development) |
| 23 | Size of Visual Asset images should be 560*292(Creative) |
| 24 | In Review websites ‘Powered by TechWyse’ and TechWyse logo should not be present in footer |
| 25 | Images should not be blurred/stretched(Creative) |
| 26 | Ensure Figma logins are updated in the creative tickets(Creative) |
| 27 | Footer Copyright Message(Creative & Development) |
| 28 | Email template Message, Thank you page, Newsletter, Error page message and color should be updated in the correct format (Creative & Development) |
| 29 | The logo in WP admin login page should be linked to website.(Development) |
| 30 | Site Speed should be above 80 and if not proper note should be added. Should ensure Code side, (CSS, Image optimization).(Development) |
| 31 | A page without content should be marked as nofollow ,noindex and also made sure that these nofollow, noindex tag should be removed after adding contents to those pages. |
| 32 | Ensure that 404 is set up properly and ‘Click Here’ link is directing to Site Map page |
| 33 | Bottom to top button should work perfectly |
| 34 | The URL structure for the blog should be domain.ca/blog/ and for the individual post it should be as domain.ca/blog/postname even if the blog comes as a submenu |
| 35 | Mail template of the site should display the correct number ie, client’s Direct inbound number (the Direct number we have purchased in CallLuge for the client). |
| 36 | In case of Landing page, Mail template should display the paid number. |
| 37 | Should ensure the blogs are publishing on the correct date on the site after the scheduled date. |
| 38 | Should make sure no errors are showing in the console during the WyseWork and live launches of the LP.(Development) |
| 39 | Category pages should be noindex,nofollow. |
| 40 | Author page should be index,follow. |
L1 – SEO
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Featured image should be shown while sharing blog in Facebook and Google plus |
| 2. | Check availability of GA Code in all the pages |
| 3. | Ensure whether the GA is linked to GTM and linked to master account in AdLuge. |
| 4. | Check availability of AdLuge’s ‘Visitor tracker’ Code in all the web pages |
| 5. | Check whether all forms are working perfectly and redirecting to Thank You page of the same site |
| 6. | Ensure ‘robots.txt‘ file is present and not blocked for Search Engine |
| 7. | Check page Title in all pages (Ensure there are no spacing issues, spell errors and special characters) |
| 8 | Ensure the presence of image alt as per the optimized doc |
| 9 | Check Meta Description |
| 10 | Check interlinks (This link should open in same tab) |
| 11 | Check External link (Link should open in new tab) |
| 12 | Check for Header and Footer optimization |
| 13 | Make sure that XML Sitemap is generated |
| 14 | AdLuge lead source and page source verification for all forms in the site |
| 15 | Spelling and Grammar check for title and meta description |
| 16 | Canonical Redirections and 301 redirection for already indexed pages |
| 17 | Ensure no broken links across the site |
| 18 | Ensure Heading hierarchy is followed for H1, H2, H3 etc |
| 19 | Ensure that content is updated in the website as per ticket notes |
| 20 | While testing a form — In Comments field the test data entered should be ‘Test mail from TechWyse. Please disregard’ |
| 21 | Blog posts should not say ‘Posted by Admin’ |
| 22 | Ensure that test leads are in Spam folder in AdLuge |
| 23 | Ensure that ‘Read More’ tags are implemented for Blogs in Blog page |
| 24 | Ensure that requirements in ticket are done perfectly |
| 25 | During Setup phase the Website Account type in Manage Websites in AdLuge should be ‘Setup’ (For Organic Optimisation) |
| 26 | Default image should be set in Blog page in case of no featured images |
| 27 | Check for broken links (URLs), If testing LIVE site, check for any ‘wysework’ or ‘techintl’ URL’s and replace them with the correct URLs |
| 28 | Given Keywords should be updated correctly under corresponding Client names |
| 29 | A page without content should be marked as nofollow ,noindex and also made sure that these nofollow, noindex tag should be removed after adding contents to those pages. |
| 30 | Should ensure there are no pirated images ( copy-rights-protected images without proper licenses) are used in blogs. |
| 31 | Once the CAN team approves the implementation, the SEO Lead will add a note, tagging Arjun if any URL changes or significant alterations affect PPC. |
| 32 | All recommendations in the roadmap should covered in the implementation document.The QA team will cross-verify this and note down any roadmap points missing from the implementation document in their notes.QA team will also confirm that all recommendations in the document are correctly implemented. |
L2-SEO
| 1. | Should ensure the client’s Google Analytics 4 (GA4) account is transferred to the secondary email ID (adluge.analytics@gmail.com) during cancellation. |
L1-Local GMB setup
| 1. | Ensure the changes made on the client’s live GMB profile page accurately reflect the data on the approved optimisation doc. |
L2 – QA Standards
L2 – PROGRAMMERS
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Selected item should be highlighted in the menu (Stage selection) |
| 2. | Use space after each punctuation “ . , ; ! : ”. (After phrases/punctuation no full stop) |
| 3. | Do not use underscore for connecting words in file names. Use hyphen (-). Eg: “about-us.php” |
| 4. | Spelling – Should be checked for correctness |
| 5. | Browser Compatibility: Windows IE8, 9, 10, 11, Firefox and Chrome. Optional: Safari and Opera |
| 6. | Operating System – Windows, Linux, Mac |
| 7. | Date-picker should have option to select the date, month and year |
| 8. | The search functionality should return the correct results according to the search keyword |
| 9. | Is the submit/Update button disabled/hided after clicking if hourglass is not implemented |
| 10. | Check whether the strip-slash function is implemented |
| 11. | Footer copyright year should be dynamic |
| 12. | By default last entered record should be shown first unless specified otherwise |
| 13. | Make sure that paragraphs and line breaks in user side are applied as per entered in admin editor |
| 14. | Radio Button – Default should be selected |
| 15. | Pagination should work properly considering the search term and the page filter |
| 16. | Dropdowns – In case of related dropdowns make sure that the child dropdown changes according to the parent dropdown. Eg: State and city dropdowns |
| 17. | No Directory path should be accessible. For this .htaccess should be configured properly |
| 18. | Client admin logins should be created with limited privileges and as per the requirement |
| 19 | Ticket should be forwarded to SEO before launch. |
| 20 | Salt key must be added to the live site Eg:  |
| 21 | Check via VPN tool with different locations like Canada/US etc to ensure the updates are reflected on the site. |
| ADMIN SIDE |
| 1. | Password field should be masked /encrypted and should have minimum 6 characters. |
| 2. | Should follow unique/primary key constraint while adding/editing records wherever it is applicable. |
| 3. | Ensure Dropdown fields are in alphabetical order by default, especially when ajax is used and it should auto select. |
| 4. | Ensure that valid labels are present for each field. |
| 5. | Validate the input with Data Type and Maximum Length. |
| 6. | For images it should auto resize if it is used for thumb and should not break or stretch at the user side. |
| 7. | Ensure all operations in a form such as Add, Edit, Delete and Update are performed well. |
| 8. | On Add Mode ensure that Save and Cancel button are available. |
| 9. | On Edit Mode ensure that Update and Cancel button are available. |
| 10. | Provide the valid tooltip using an icon near text box if specified. |
| 11. | Mention the image/file type or size if it accepts only a particular type/size. This should be mentioned below the field. |
| 12. | Akismet API key should be enabled by default. |
| 13. | In Blog page default number of blogs should be 5 per page or as per given in id8. |
| 14 | If the ticket is not sent to SEO team after GTM/GA implementation for ensuring real time tracking |
| FORM ALERT MESSAGES |
| 1 | Clear cache and cookies before the form verification |
| 2 | First Name: Please enter your First Name. |
| 3 | Last Name: Please enter your Last Name. |
| 4 | Name: Please enter your Name. |
| 5 | Email: Please enter your Email Address. (Invalid Email Address) Sorry, you have entered an invalid Email Address. |
| 6 | Address: Please enter your Address. |
| 7 | City: Please enter your City. |
| 8 | State: Please select a State. |
| 9 | Zip/Postal Code: Please enter your Zip/Postal Code. |
| 10 | Comments: Please enter your Comments. |
| 11 | Username Please enter your Username. |
| 12 | Verification Code: Please enter Verification Code. (Invalid Verification Code) Please re-enter a valid Verification Code.(Verification Code mismatch) Please re-enter a valid Verification Code. Please select the Square and click the Submit button.Please select the Triangle and click the Submit button.Please select the Diamond and click the Submit button.Please select the Circle and click the Submit button.Please select the Star and click the Submit button. (When shape Captcha is not selected) “The Shape you selected is incorrect, please select the right one.”(Invalid Shape Captcha) “Incorrect answer, please select the right Shape.” |
| 13 | Punctuation |
| 1. Proper spacing | |
| 2. Exclamation marks as per the standard format | |
| 3. Full stops after title/phrases | |
| 4. Hyphens without a space before and after words | |
| 5. Spellings for all evident texts and form elements. | |
| 6. Use 3 dots (periods) at the end of incomplete contents | |
| Admin side- Alert messages | |
| Username: Please enter your Username OR You have entered an invalid Username. Please re-enter a valid Username. | |
| Password: Please enter your Password.(Invalid Password) You have entered an Invalid Password. Please re-enter a valid Password. | |
| Current Password Please enter your Current Password. | |
| Delete Are you sure you want to delete the Selected Record(s)? | |
| Image The image does not meet the specified size criteria (width * height) in pixels. | |
| Search field empty Please enter a Search Keyword. | |
| Before and After image validation Please select Before & After Images. |
WP- Security L2 – PROGRAMMERS
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Akismet is activated. |
| 2. | Versions and Plugins are upgraded. |
| 3. | Security Plugins are installed (Wordfence etc). |
| 4. | Editor should be disabled for regular users under Appearance and Plugins. Administrator login should have full access at all times. |
| 5. | The option ‘Allow link notifications from other blogs – Pingbacks and trackbacks’ in ‘Discussion settings’ (Coming under settings) should be unchecked by default. |
| 6. | Database Table prefix and Security keys should be unique. |
L2 – DESIGNERS
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Menu structure should be consistent. |
| 2. | Page title should be meaningful and no duplicates. |
| 3. | Always use the Organization standard for Abbreviation Eg: USA |
| 4. | Use space after each punctuation “ . , ; ! : ”. (After phrases/punctuation no full stop) |
| 5. | Do not use space before or after “–” and ‘/’, when it is used for connecting two words. |
| 6. | Font Format: |
| 7. | Do not use underscore for connecting words in file names. Use hyphen (-). Eg: “about-us.php”. |
| 8. | All the field labels having multiple words should be in Title Case. Eg: “Confirm Password” |
| 9. | Logo should direct to the home page of the site. |
| 10. | Alt tags should be descriptive (except for bullet, icon images and buttons) |
| 11. | Is HOME tab placed in the blog and directed to the home page of the site. |
| 12. | BLOG tab should be placed in the blog and linked to the blog home page. |
| 13. | Check for the Alignment, formatting and readability of content. |
| 14. | Browser Compatibility: Windows IE8, IE9, 10,11, Firefox Chrome, and Safari. Optional: Opera. |
| 15. | Operating System – Windows, Linux, and Mac |
| 16. | Phone number should be clickable in iPhone and iPad |
| 17. | Look and feel should be consistent. |
| 18. | Check if the favicon is added for site and blog. Ensure 16*16 pixel. |
| 19. | Are 3 periods used at the end of incomplete static contents? |
| 20. | Check if the Read more button/link is provided in proper way. i.e “Read More” button. |
| 21. | Top padding for Labels of text box and text area should be consistent. Alignment should be left by default. |
| 22. | Textarea ‘overflow’ property should be set to ‘auto’. |
| 23. | Check if RSS feeds directing to the correct URL. |
| 24. | Check for Google +buttons, Youtube, Facebook, Twitter buttons and Counters social icons in the site and ensure these are linked to the correct social media pages and should open in new tab. |
| 25. | Ensure that a menu item has an icon symbol if a sub-menu exists. |
| 26. | If a flash banner is used in a concept, a static image should also be created and approved for use in tablet/phones where flash is not present. This should be implemented using if condition based on Browser Agent or Device meta rules. |
| 27. | Testimonial needs open and close quotes. |
| 29 | Make sure the “NoFollow” to be removed in the Text and Footer logo as well. |
| 30 | Dropdown field – should display “Select” as default. |
| 31. | External links should open in new tab. |
| 31. | The logo in Thank You page of Landing page should redirect to Landing page. |
| 32. | Ensure there is no duplication in content. |
| 33. | Titles in Pop up form and button should be same. Should be consistent in mail template too. |
| 34. | New Error page message:Sorry! Page not found.Click Here to visit our sitemap to find what you’re looking for or contact us directly if you require assistance! |
| 35. | New Thank You message:“Thank you for contacting us! We’ll be in touch shortly.” |
| 36. | Message after submitting Career Application:Thank You. Your application has been received and you will receive a confirmation email to the email provided.In Email template: We thank all applicants for their response; however only those considered for an interview will be contacted. |
| 37. | Message for Newsletter subscription:Thank You for subscribing to our Newsletter. A confirmation email has been sent to the address you provided. |
| 38 | “Read More” and other buttons should be aligned right (From the creative phase itself) |
| 39 | Ensure that white space is not seen in the bottom of the site. |
| 40 | Indenting the following in the content section: Bullet Points, Numbered Lists, Images (if not text wrapped) |
| 41 | A designer should review the site for overall formatting and end user usability. |
| 42 | In the design phase itself breadcrumbs should be added to the site for Woocommerce sites. |
| 43 | Ensure “no follow” tag for external links(If required) |
| 44 | Pagination should work properly considering the search term and the page filter |
| 45 | Check the site in resolution 1366*768, 1440*900,2560*1440 |
| 46 | Check via VPN tool with different locations like Canada/US etc to ensure the changes are reflected on the site for the Nitropack clients.(There should no nitropack cache on the site) |
| 47 | Do not link the header tags of any section/fold to their dedicated pages. This should be checked across the entire site. |
| ADMIN SIDE |
| 39. | Ensure that valid labels are present for each field. |
| 40. | Follow navigation naming standards – Manage/Module Name. |
L2 – SEO
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Ensure that content spelling is correct and relevant. |
| 2. | Ensure “no follow” tag for external links(If required), |
| 3. | Spacing should be consistent in the content section |
| 4 | Indenting should be given in the content section |
L3 – QA Standards
| Sl. No. | ISSUE DESCRIPTION |
| 1. | Issues that includes 3rd party CMS, system compatibility, and unusual verification mismatch |
===================================================
=====
Current Email Template: Thank you for contacting Company Name. Your request has been sent and one of our representatives will contact you at our earliest convenience. For your own reference, these are the details that you have sent us.
Thank You Page: “Thank you for contacting us! We’ll be in touch shortly.”
Footer Copyright Message
1. © 2017 Family Cosmetic Dentistry, Smile Makeovers, Porcelain Dental Crowns, Implant Dentistry. smiletoremember.com. All Rights Reserved.
2. Varied Anchor Texts will be used for the Web Designs – (If we did only design or
blog)
“TechWyse Digital Marketing”
“Digital Marketing by TechWyse”
“TechWyse SEO Agency”
“TechWyse Digital Agency Canada”
“TechWyse SEO Services Toronto”
“TechWyse Web Design Agency” etc
3. Powered by TechWyse – (If we did both or only Internet Marketing)/ Landing Pages