My List ♥ ()

Formula Content Analysis Fields

Source Type: Formula

Formulas can be used to derive values from other fields, for instance pulling out URL "folders" from URLs.

In Content Chimera

You can create Excel-like formulas in Chimera. In addition, Chimera automatically calculates many useful values (like folder1) rather than you having to put in the formula.

See Formula 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).

Content Type ♡

Content Type (semantic type of content, such as Product Page or Event) is usually an extremely effective way to group and look for patterns across a digital presence.

General Usefulness:

Ease of Automation:

Compare with other Category fields.

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:

Compare with other Quality fields.

Disposition ♡

This is the treatment a piece of content will get during a transformation.

General Usefulness:

Ease of Automation:

Consider instead: Effort

Division ♡

The organizational division (or department, vice presidency, company, etc) that owns the page.

General Usefulness:

Ease of Automation:

Compare with other Org fields.

Effort ♡

Expected manual effort to transform the content item.

General Usefulness:

Ease of Automation:

Compare with other Decision fields.

File Format ♡

File format (as opposed to content type) is the actual format of the file as delivered by the web server (PDF, HTML, etc). This is especially useful for sites with a large amount of non-HTML.

General Usefulness:

Ease of Automation:

Consider instead: File Group

File Group ♡

On particularly complex digital presences, there may be so many file formats that seeing all of them in charts or presentations is confusing. File Group groups the file formats, for instance "Data or Spreadsheet" to capture CSV and Excel files.

General Usefulness:

Ease of Automation:

Compare with other Basic fields.

Folder1 ♡

Folder1 is the first "folder" in the path, such as "blog" in "test.com/blog/". This is often an effective proxy for site section.

General Usefulness:

Ease of Automation:

Consider instead: Site Section

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.

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

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

Site ♡

Within which site (as experienced by the site visitor) does this content appear?

General Usefulness:

Ease of Automation:

Consider instead: Site Type

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.

Source System ♡

Where is the primary source of content for this URL? For instance, what CMS, document management system, or product information system does this content primarily come from?

General Usefulness:

Ease of Automation:

Compare with other Category fields.

Unique Content ID ♡

An ID unique for the piece of content. This should be unique across the entire list.

General Usefulness:

Ease of Automation:

Compare with other Basic fields.

Legend