An Azure DevOps task that generates a report after analysing the meta tags of each page on your website.
Preface: We all agree how important meta tags are to our website. It helps describe the contents of a page and thereby providing more useful information for search engines to display. You can also dictate what information is shown when you share a page from your website on social media.
Meta Tag Analyzer is an Azure DevOps task that provides you with the ability to automatically run a check on your website and generate a report of the meta tag information. Benefits:
- Assurance: Ensure that your last release hasn't changed anything unexpectedly that will be impact your online presence
- Automatic and part of your value stream: Don't neglect the significance of meta tag content by checking this on a one-off basis. Include this as part of your pipeline and part of each release artifact.
- Comprehensive and easy to read: Simply download this report and email it to the team that looks after your online presence.
Meta Tag Analyzer Azure DevOps task will:
- Generate an Excel report after analysing the meta tags of all your pages (Download sample report).
- Log the analysis to the console too, so you get the same information from within the pipeline itself.
Install Meta Tag Analyzer extension for your Azure DevOps pipeline from this page. Refer to Microsoft's documentation page if you need help installing an extension, in general.
Adding the task
Next, in your build or release task, click on Add a new task and search for Meta Tag Analyzer. Click on Add.
||URL to the sitemap file of your website. Your sitemap file must follow this pattern.
||Customize the name of the Excel report generated by this task. Only include the file name and not the file extension. If left blank, default report name will be
meta-tag-analyzer-report.xlsx. You can also use a variable to generate the report name. Example:
MetaTagReport-$(Build.BuildNumber) appends the build number to the filename.
Downloading the report
This task generate the report in the working directory but doesn't copy the file to the drop location. If you'd like the file to be included in the artifacts, ensure you explicitly include it. Read more for ideas around this.
What about adding it to the release definition?
Since you cannot publish artifacts from your release definition, ensure you either:
- Upload the generated report to an external file server, storage account or a web app's folder, or;
- Trigger a 'post release' build from the release pipeline.
Read more for ideas around this.
Refer to the detailed release notes found here.
Meta Tag Analyzer (c) 2019 Clyde D'Souza