iQWEB FAQ

Questions, Answered

A clear explanation of what iQWEB does, what it does not do, how the signals are used, and why agencies use it to turn raw diagnostics into structured client-ready reporting.

What it is

Structured diagnostic reporting

iQWEB is designed to turn multiple website diagnostics into a report agencies can actually use with clients, instead of leaving the work spread across separate tools and screenshots.

What it is not

Not just a Lighthouse wrapper

Performance data is one part of the picture. iQWEB also layers technical SEO checks, trust indicators, baseline comparison and AI visibility signals into one report structure.

Why people use it

Time saved and reporting clarity

The value is not the existence of individual checks. The value is reducing manual reporting work and making the results easier to explain, prioritise and track over time.

The short version

The platform exists to close the gap between raw diagnostics and client communication.

Free tools are useful for raw measurement. iQWEB is built for the next step: combining multiple signals, identifying what matters, capturing baselines, and turning that into a report a developer or agency can actually hand to a client.

Frequently asked questions

iQWEB is a website diagnostic reporting platform built for web developers, agencies, consultants and technical service providers who need a faster way to turn technical checks into client-ready output.

The platform analyzes multiple signal groups including performance, technical SEO, trust indicators and AI visibility, then organizes those findings into a structured report that is easier to explain, prioritise and compare over time.

No.

Lighthouse and PageSpeed Insights are valuable diagnostic tools, but they primarily provide raw performance data. They do not aim to package multiple signal groups into a reporting workflow designed for agency delivery, baseline comparison and client communication.

iQWEB uses performance signals as one part of a broader report that also includes technical SEO checks, trust indicators, AI visibility analysis, prioritised issue presentation and baseline tracking.

In simple terms: Lighthouse helps measure. iQWEB helps measure, organise, explain and present.

Performance
Delivery metrics and Core Web Vitals related to loading speed, rendering behaviour and user experience.

SEO
Technical SEO indicators such as titles, meta descriptions, structural elements and other site-level signals that influence discoverability.

Trust
HTTPS, security headers and related trust indicators that affect technical credibility and user confidence.

AI Visibility
Signals that help determine whether a site or brand appears in tested AI recommendation prompts within its detected category.

AI Visibility is a directional signal that tests whether a brand or website appears in AI-generated recommendation prompts relevant to its business category.

The platform first detects the likely category of a site, then evaluates visibility within tested prompts related to that category. It also considers contextual signals that may support or weaken visibility, such as entity relevance, mentions and site context.

This signal is intentionally called AI Visibility rather than AI ranking or GEO certainty. AI outputs can vary by prompt, model and time. The purpose of the signal is to surface patterns and give agencies a starting point for discussion, not to claim a permanent or absolute truth.

No.

The report is based on measurable technical signals and structured diagnostic logic. AI may be used in limited areas to support interpretation or visibility testing, but the platform is not simply inventing a report from thin air.

In other words, the report is anchored in underlying diagnostics. It is not intended to be vague, generic output detached from measurable evidence.

Scores are derived from the signals collected within each category and the severity of issues detected. They are designed to function as diagnostic indicators that help identify where attention may be needed.

A score should not be treated as a universal ranking of a business or website. It is a structured summary of the signals available at the time of testing.

The more important part of the report is not the number alone, but the explanation of what is influencing the result and what should be fixed first.

Baseline lets an agency or developer capture a diagnostic snapshot of a site at a specific point in time.

Future scans can then be compared against that reference point to show what improved, what regressed and where additional work may still be needed.

This is especially useful in client work where the goal is not just to find issues once, but to demonstrate measurable progress after optimisation.

Free tools are valuable and many developers already use them. The problem usually is not access to raw checks. The problem is the manual work required to combine those checks, interpret the results, package them cleanly and explain them to clients.

iQWEB exists to reduce that workload by bringing multiple signal groups together into one structured report with clearer priorities, baseline support and client-ready presentation.

For solo developers and agencies, the main value is often workflow compression: less time collecting, less time formatting and less time rewriting diagnostics into plain English.

The pricing is not based on the existence of a single metric or on charging for one AI prompt. It is based on the time saved and workflow value created when multiple diagnostics are packaged into a structured agency-ready report.

In many client workflows, the costly part is not opening Lighthouse or checking a few technical signals. The costly part is combining multiple sources, deciding what matters, preparing a usable report, explaining the findings and then tracking changes over time.

iQWEB is intended to reduce that repeated manual effort. For agencies and consultants producing reports regularly, the value is usually in reporting speed, consistency and presentation clarity.

No.

iQWEB is designed as a diagnostic support and reporting tool. It highlights issues, patterns and opportunities, but it does not replace engineering judgement, implementation skill or business context.

The best results come when developers use the platform as a reporting and analysis layer, then apply their own expertise to the final recommendations and fixes.

No diagnostic system should be treated that way.

Website analysis depends on the data available at the time of testing, the condition of the site, and in some cases external APIs or AI systems that may change over time.

iQWEB should be treated as a structured snapshot and decision-support tool, not a claim of permanent certainty. That is also why ongoing refinement, baseline comparison and real-world developer feedback remain important.

iQWEB is developed by iQLABS Ltd, a New Zealand technology company focused on building practical, engineering-led software tools.

The product is being built as a focused platform for website diagnostics, structured reporting and agency workflow improvement, with continued refinement based on real-world testing and user feedback.

The intention is not to produce a generic AI wrapper. The intention is to build a usable product with clear reporting value, transparent positioning and ongoing improvement.

Next step

Want the deeper explanation?

The FAQ answers the main positioning and trust questions. The Methodology page should go further into signal logic, data inputs, AI Visibility framing and limitations.

Recommended next page

Create a dedicated Methodology page and link it in the main nav so developers can quickly inspect how the platform works.

Open methodology page