Last active
February 1, 2017 09:49
-
-
Save zallek/74f4a9ad0fcd5dde646e5b74a32c19ee to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| url | |
| http_code | |
| depth | |
| date_crawled | |
| [...segments] (one column by segment) | |
| title | |
| h1 | |
| h2 | |
| h3 | |
| description | |
| compliant | |
| compliant_reason_canonical | |
| compliant_reason_content_type | |
| compliant_reason_http_code | |
| compliant_reason_noindex | |
| internal_page_rank | |
| internal_page_rank_position | |
| number_of_inlinks | |
| number_of_outlinks | |
| number_of_outlinks_follow | |
| number_of_outlinks_no_follow | |
| delay_first_byte | |
| delay_last_byte | |
| [visits.organic.all] | |
| [visits.social.all] | |
| [search_engines.google.crawls.count] | |
| [search_engines.bing.crawls.count] | |
| [...extracts] (one column by existing extract) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Columns headers should be the verbose names (ex: "Full URL" for "url" field)
If a feature isn't enabled do not create the related column.
Ex: if the analysis doesn't have search engines feature, do not add the related columns.
Ex: if the analysis only define 1 segment, only create 1 column.