Content Analysis DB > Fields > Field Types > My List ♥ ()

User Fields for Content Inventories, Audits, & other Analysis

Field Type: User

Ultimately we want to make it easy for users to complete certain tasks. Sometimes we can directly capture this type of metric, but usually we need to confine ourselves to metrics that are more removed from the actual user experience.

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

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.

②. 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.

③. 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).

Audience the content is actually written to target (whether or not it is supposed to).
General Usefulness:
Ease of Automation:
Page Views
Page views are often the first thing to be added from an additional source, after the basic rows of content in the inventory/audit have been determined. Although not always the most useful metric for the value of content, it's often the most immediately tangible proxy.
General Usefulness:
Ease of Automation:
Consider instead: [Success Event] Count
Reading Level
Reading Level represents the education level required to understand text. Since much content is overly complex, this can be useful to identify where there may be education requirement mismatches.
General Usefulness:
Ease of Automation:
[Success Event] Count
The count of events that were successful from this page, such as the count of purchases or the count of downloads.
General Usefulness:
Ease of Automation:


General usefulness is a blend of the difficulty in getting the value and how useful it is once you have it. These stars roughly correspond to:

  • ★★★ Broadly Useful. These would be worth including a most analyses.
  • ★★ Frequently useful for particular needs. These may not be quite as broadly useful, but they are frequently useful. Notably, if you have a general reason for a field that is rated two stars then you may wish to go to the category and look for others that may be slightly more useful.
  • ★ Rarely useful. These are listed since they still have a "following" or because they are easy to implement so are tempting to rely upon. Your mileage of course may vary, but in general these are less useful fields.

Ease of automation is how easy it is to get the value:

  • ⚙⚙⚙⚙ Easy to automate. Completely point-and-shoot automation (although, of course, there can be exceptions to when some information is more difficult to extract than it should be).
  • ⚙⚙⚙ Relatively easy to automate. With the right tool, this can almost certainly be automated with very limited configuration (not requiring deep technical knowledge).
  • ⚙⚙ Can probably be automated. With the right tool and some technical ability and/or time to configure (for instance, providing xpath and regex information to select content out of a page) this can probably be automated. But it probably is not just clicking a single button to set up and run (unlike the three and four gears items).
  • ⚙ Very difficult to automate. This almost certainly requires manual intervention. Note: there is a technique that can be applied in many cases to sample and then use rules and repeat.

Obviously all of the above is ratings in the general case. You may have particular needs for fields that are generally not useful, and you may already have some clean data that makes automation trivial for some elements that are more generally difficult.