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

Manual Review Content Analysis Fields

Source Type: Manual Review

This is the type of review almost everyone presumes, when someone manually reviews each piece of content to define the field value for a particular piece of content. This may be required at times, but, unless you have a small set of content, you should try to automate to be more efficient and also to iterate/improve over time.

See Manual Review fields below. Or show fields for all field types.
[Category] Revenue
Particularly useful for product or property pages, this field represents the revenue generated by this product or property (regardless of whether it was directly generated by digital channels or not).
General Usefulness:
Ease of Automation:
Compare with other Org fields.
Division
The organizational division (or department, vice presidency, company, etc) that owns the page.
General Usefulness:
Ease of Automation:
Compare with other Org fields.
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:
Compare with other Quality fields.
[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:
Compare with other Quality fields.
[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:
Compare with other Quality fields.
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
Site Type
For large scale digital presences, grouping sites by type can be a highly effective way of managing and transforming.
General Usefulness:
Ease of Automation:
Compare with other Category fields.
[Target] Field
What the *desired* field value would be. For instance, there may be an existing content type but in some cases it should be another content type (so you would have a Content Type field as well as a Target Content Type field).
General Usefulness:
Ease of Automation:
Compare with other Decision fields.
Tone
How the content is communicated with language. Tone may reasonably vary across a digital presence.
General Usefulness:
Ease of Automation:
Compare with other Brand fields.
Topic
The topic/subject of the content.
General Usefulness:
Ease of Automation:
Compare with other Category fields.
Voice
Brand voice
General Usefulness:
Ease of Automation:
Compare with other Brand fields.