My List ♥ ()

Quality Content Analysis Fields

Field Type: Quality

Quality indicators can either be the entire point of an analysis (when testing a hypothesis or understanding the pervasiveness of a problem) or they can be used to inform action (for instance, if a page has a lot of different quality issues then perhaps it should just be rewritten).

See Quality fields below. Or show fields for all field types.

Answer some questions to help select fields

If we take the traditional view of a content inventory or audit, we have rows representing each page (so each row has a unique URL) and then we have columns for things like the meta description or crawl depth. These columns are the different fields we have available to us in our content analysis.

①. Define what you are trying to accomplish.

Your content analysis needs to be grounded on your analyze goal.

Examples: Plan Digital Transformation, Test Content Hypothesis, Provide Better Bid.

②. Define your analysis approach.

Size and complexity of your digital presence

Size and complexity of your digital presence should drive your content analysis approach.

My digital presence is:

Use the calculator

Your approach

Content analysis does not necessarily mean opening up a spreadsheet. Before diving in, you should define your basic approach to the analysis.

Examples: Brute Force; Sample, Rules, Repeat; Quick Take.

③. Select fields toward your goal, grounded in your prioritized list of questions you want answered.

Although you can use this database however you like, in general we recommend that you build up a list of fields that will be useful for your analysis. To do so, just click on the heart next to any field name. After you have hearted some fields, you can see an analysis of your list at My List ♥ (at which point you can move to ④. Start iterating on your analysis, starting with the basics).

Audit Comments ♡

Free-text notes and findings recorded during a content audit. Used to capture observations, issues, and recommendations for individual pages or content assets.

General Usefulness:

Ease of Automation:

Date Published ♡

Date the content was originally published. This is frequently a useful factor in deciding what content can be culled.

General Usefulness:

Ease of Automation:

Has [Problem] ♡

Yes or no, does this piece of content have this specific problem? The actual field name would depend on your situation, such as "Has Wall of Text".

General Usefulness:

Ease of Automation:

Near Text Duplicate ♡

Is there a near text duplicate of the page? If so, what is the URL for that near duplicate.

General Usefulness:

Ease of Automation:

[Problem] Count ♡

How often does the problem happen on the page? This would be a specific issue, so something like "Left Nav Count".

General Usefulness:

Ease of Automation:

[Problem] Example ♡

An example of a problem (on a specific page) you are investigating. This field could be repeated in an analysis, with actual fields like "Table Example" or "Bad Character Encoding Example".

General Usefulness:

Ease of Automation:

Redundant ♡

Is the information redundant with respect to other content on the site? This is one of the anchors of the highly popular ROT three fields.

General Usefulness:

Ease of Automation:

Consider instead: Near Text Duplicate

Legend