All Collections
Quality Assurance
Quality Assurance: Content with QA Errors
Quality Assurance: Content with QA Errors
How to repair content with QA errors
Faith George avatar
Written by Faith George
Updated over a week ago

Section Topics


Introduction

This chapter gives information on how to use the Monsido Quality Assurance feature to locate and handle website content errors.

  1. Click Select Domain to open the Domain Overview page.

    The location of the Select Domain button in the upper left corner of the page..

  2. Click Open on the same row as the domain name.

    The location of the Open button, on the same row as the domain name.

  3. The Dashboard for the domain opens.

    The full dashboard view.

  4. Click Quality Assurance (the checkbox icon), on the toolbar.

    Image showing the location of the Quality Assurance button.

  5. The Quality Assurance page opens.

    Image of the Quality Assurance landing page.

Instructions

Click Content with QA Errors from the menu on the left side of the page.

Image showing the location of the Content with QA Errors option.

The Content with QA Errors page opens.

Image of the Content with QA Errors page.
  • On the menu bar at the top of the chart, navigate between:

    • All

    • Pages

    • PDF Documents

    • Other Documents

    • Search: Click in the dialog box and type a search parameter.

    • Filter (the funnel icon): Click to filter for:

      • Labels

      • Languages

      • Contains.

  • The table with the results has the headers:

    • Title and URL: This is the title and URL of the content that has been targeted with errors. Click the URL. The Broken Links page opens.

    • Notifications: Here you see the number of notifications per page.

      1. Click the number on the same row as a Title and URL to expand a quick-info box on the notifications for the URL.

        The expanded Notifications box.

        • Broken links: Informs about the number of broken links found.

        • Broken images: Informs about the number of broken images found.

        • Misspellings: Informs about the number of misspelled words found.

      2. Click on the number on the same row as the error to navigate to the errors page.

      3. Click Action on the same row as an error to expand the available actions.

      • Choose between:

        • Add to dictionary

        • Add to dictionary for all languages

        • Ignore

        • Mark as Read.

    • Priority: Low, Medium, High as determined by the number of page views.

      For more information, see the User Guide chapter.

    • Views: Approximate number of page views since the last scan. This information is only available when Statistics is enabled.

      For more information, see the User Guide chapter:

    • Open page details (the page icon): On the same row as a page, click Open Page Details.

      Image showing the location of the Open Page Details button, on the same row as a page.

      The details pane slides open. View the issues on the page, rated per severity, as determined by the last scan.

      Image showing the landing page for the page details view. The default selection shows Broken Links / All.

    • From the menu on the left, navigate between:

      • Broken Links (landing page default): This page shows the full address of the broken link.

        For more information, see the User Guide chapter:

      • Broken Images: This page shows the location of broken images.

        For more information, see the User Guide chapter:

      • Misspellings: This page shows the list of misspelled words.

        For more information, see the User Guide chapter:

      • Potential Misspellings: This page shows the list of potentially misspelled words.

        For more information, see the User Guide chapter:

      • Ignored Misspellings: This page shows the list of ignored misspellings.

        For more information, see the User Guide chapter:

      • Readability: This page shows the readability score for the URL.

      • For more information, see the User Guide chapter:

    • Open page details (the page icon): Click to navigate to the page URL and view the page as an external visitor.

      • Action: Click to designate the issue with:

        • Mark as fixed: Marks the issue as fixed. It will be included in subsequent scans and if the error returns, it will appear again in the broken links list. Select this option when the error is actually fixed by the web team on the HTML code of the webpage, or if it is a temporary (for example, in an unpublished state) known issue.

        • Mark as ignored - Use this option:

          • If links are incorrectly marked as broken.

          • To ignore spelling issues on a single-page basis.

          • To ignore all other issues on a domain level.

          Note: The difference between Mark as Fixed and Ignore is that issues marked as Fixed are still included in future scans and can be flagged again if the error persists. Issues that are set to Ignore are permanently omitted from future scans and compliance scores.

      • Redirect to Page (magnifying glass icon): Navigate to the page and then use the Monsido Extension to identify the placement of the errors on the page, repair the errors, and more.

        For more information, see the User Guide chapter:


Additional information:

For more information, see the User Guide chapters:

Tip! The Monsido Color Contrast Checker is a quick way to test the color combinations on websites and pages.

For further assistance, contact the Monsido support team at support@monsido.com or via the Monsido chat and help features inside the application.

Image showing the location of the Help and Support buttons on the Dashboard

See Monsido for Developers for documentation and advanced help files including SDK information for developers.

Contact us

Monsido, an Optimere brand:

San Diego, CA, USA

5880 Oberlin Dr,
San Diego, CA 92121, USA

Australia & New Zealand

Suite 2.04
80 Cooper St
Surry Hills, NSW 2010

Copenhagen, Denmark

Borupvang 3
2750 Ballerup, Denmark

London, UK

14 New Street
London, EC2M 4HE

Did this answer your question?