Website Auditing via Dynamic Code Execution Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing website auditing mechanisms are inefficient in validating page tags and other scanned content, often providing incomplete or inaccurate reports due to the inability to determine if embedded code executes properly and misses dynamic content, leading to issues with website health and optimization.

Innovation Solution

A system that automatically audits websites by validating page tags against vendor and user validation rules, using a combination of web page scanning and rendering techniques to ensure that page tags conform to specific requirements and that embedded code executes correctly, providing a comprehensive report on website health and optimization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If conventional scanning mechanisms are used to check for presence of expected metatags and tracking pixels, then the auditing process is simple and fast, but the validation is incomplete and inaccurate as it cannot determine if the code executes properly or meets vendor requirements

Engineering Contradiction:
Improvevalidation accuracyVSAvoidauditing system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a rendering engine as an intermediary component between the scanner and the validation process. The rendering engine executes the embedded code (JavaScript, AJAX, etc.) in a controlled environment, capturing the actual runtime behavior and data. This intermediary allows the system to move from static text scanning to dynamic execution validation, determining whether code not only exists but also executes properly and meets vendor requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical scanning approach (simple text searching for metatags and tracking pixels) with a more sophisticated rendering and execution mechanism. Instead of merely checking for the presence of code strings, the system uses a rendering engine to interpret and execute the code, substituting the simple mechanical scan with a simulated browser environment that can evaluate code functionality and outcomes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If automated mechanisms generate site maps by scanning web pages, then the process is efficient and requires minimal human input, but the generated maps are inaccurate and incomplete when pages fail to load properly or require human input

Engineering Contradiction:
Improvesite map generation efficiencyVSAvoidsite map accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies dynamics by making the site map generation process adaptive and responsive to actual page behavior. The rendering engine dynamically executes page code and observes runtime conditions, allowing the system to handle various scenarios (failed loads, required human input, dynamic content) flexibly. This dynamic approach enables the system to distinguish between pages that appear to load successfully but contain errors and those that truly function correctly, improving accuracy while maintaining automation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent implements feedback mechanisms where the rendering engine continuously monitors page execution and provides information back to the site map generation process. When pages fail to load properly or require human input, the system receives feedback about these conditions and adjusts its behavior accordingly, such as marking those pages as problematic or excluding them from the automated map generation, thereby improving the reliability of the generated site maps.

Inventive Principle:
Principle #23Feedback

3Loss of information

If the system scans web page source code text for expected metatags and tracking pixels, then the auditing process is quick and resource-efficient, but it misses dynamic content and cannot validate if embedded JavaScript routines execute appropriately

Engineering Contradiction:
Improvedynamic content detectionVSAvoidauditing resource consumption
Core Design Contradiction:
Loss of informationVSUse of energy by moving object

Solution Approach 1:

The patent applies partial action by selectively rendering and executing only the embedded code portions that are relevant to validation, rather than processing entire web pages. The system identifies specific JavaScript routines, AJAX calls, and other embedded code elements that need validation and executes only those in the rendering engine, leaving the rest of the page scanning as simple text operations. This partial execution approach captures dynamic content information while limiting resource consumption to only what is necessary for validation.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9606971B2Rule-based validation of websites
Publication Date: 2017.03.28 OBSERVEPOINT LLC
  • US9606971B2 patent drawing
  • US9606971B2 patent drawing
  • US9606971B2 patent drawing

AI summary

An automated website analysis system includes mechanisms for automatically auditing a website to validate that the scanned web page information conforms to validation rules. In one implementation, an auditing system requests web pages of an identified website pursuant to validating at least a portion of each requested web page. Embodiments include scanning page code of at least one of the web pages to identify scanned web page information, including a page tag. The scanned web page information is validated to determine whether is conforms to at least one validation rule by validating variables of the page tag against validation rules, including a vendor validation rule. Results of the validation are reported.