QuinnInteractive\Seo\Analysis\Analysis

Class Analysis

Synopsis

class Analysis {

• // members
• protected  $domParser;
• protected Page|PageHealthExtension $page;
• protected  $result;
• protected  $resultLevel;
• private static array $hidden_levels = ;
• private static array $indicator_levels = ;
• // methods
• public void __construct()
• public string getContent()
• public SiteTree|PageHealthExtension getPage()
• public simple_html_dom getRenderedHtmlDomParser()
• public int getResult()
• public ArrayData inspect()
• public array responses()
• public int run()
• public $this setPage()
}


Hierarchy

Uses

• SilverStripe\Core\Injector\Injectable
• SilverStripe\Core\Config\Configurable

Members

private

• $hidden_levels — array
  Allows you to hide certain levels (default, danger, success) from appearing in the content analysis.
• $indicator_levels

protected

• $domParser
• $page — \Page|PageHealthExtension
• $result — int
• $resultLevel — string
  One of: default, danger, warning or success

Methods

public

• __construct() — Analysis constructor.
• getContent() — Fetches the rendered content from the dom parser. This is why it's important that your templates are semantically correct. `<div>` tags should be used for layout and positioning purposes and using `<p>` tags for content is semantically correct. Semantically correct pages tend to rank higher in search engines for various reasons (such as how effectively crawlers parse your website etc.).
• getPage()
• getRenderedHtmlDomParser()
• getResult()
• inspect()
• responses() — All analyses must override the `responses()` method to provide response messages and the response level (which is used for the indicator).
• run() — You must override this in your subclass and perform your own checks. An integer must be returned that references an index of the array you return in your response() method override in your subclass.
• setPage()