AI-097 | AI/Codex

Codex-Assisted Website QA Report

Codex-assisted website QA workflow covering pages, links, forms, responsive checks, evidence, priorities, and handoff

Arifur Rahman reviews an agreed set of public or authorized website pages and priority flows for broken links, form behavior, browser-console issues, failed resources, and desktop, tablet, and mobile layout problems. You receive a prioritized issue report with affected URLs, evidence, reproduction steps, and clear verified, failed, or not-tested boundaries.

How it works

A agreed-scope service with a clear start path.

Send the request, book the free 15-minute call, and I confirm what I need before work starts.

1 Request

Send your contact details, page or tool link, deadline, and the result you want.

2 Review

Use the free 15-minute consultation to confirm fit, inputs, and next step.

3 Start

Confirm the agreed-scope, access boundary, start date, and handoff expectation.

Good fit

  • Your site recently launched or changed and the important customer paths need a structured review.
  • You are unsure whether navigation, links, forms, confirmations, redirects, or responsive layouts behave as expected.
  • You need browser-console and failed-resource findings translated into a practical issue log.
  • You can define the pages, expected behavior, access boundaries, and whether form submission is authorized.
  • Visitors or team members report inconsistent page, link, form, or mobile behavior.
  • A form appears complete, but validation, confirmation, notification, or routing has not been verified.
  • Browser-console errors or failed resources may be affecting a priority page or flow.
  • Issues are discussed informally, without affected URLs, severity, reproduction steps, evidence, or ownership.

Common request language

Use this gig when your request sounds like this.

  • agreed-scope website QA report for priority pages, links, forms, console errors, and responsive layout.
  • Pre-launch website QA audit with reproducible issue notes and severity.
  • Website form and confirmation-path testing using authorized no-private-data QA values.
  • Desktop, tablet, and mobile website review for selected customer journeys.
  • Browser-console, failed-resource, broken-link, and redirect review for agreed URLs.
  • Website QA handoff report separating verified, failed, and not-tested checks.

How I can help

What I will complete in this agreed-scope.

Start with a free 15-minute discovery call. We will discuss your project goals, current setup, scope, timeline, and cost, then agree a written proposal before any work starts.

this audit covers one agreed website and a bounded URL or priority-flow list. I review page and navigation behavior, links and redirects, authorized form paths, browser-console and failed-resource signals, and representative desktop, tablet, and mobile layouts. Authenticated paths are checked only with approved temporary access, and forms are submitted only when explicitly authorized with clearly labeled no-private-data QA values.

Codex may assist with systematic collection and organization, but Arifur Rahman reviews the scope, findings, priorities, and handoff. This is a point-in-time QA report, not an unlimited crawl, accessibility certification, legal compliance review, security penetration test, production-fix package, or guarantee that every browser, device, defect, ranking, traffic, lead, or conversion outcome has been covered.

  • Agreed page inventory, priority flows, expected behavior, browser or device priorities, and test boundaries.
  • Page, navigation, internal and external link, redirect, and obvious status-path review for the agreed URLs.
  • Form input, validation, confirmation, and routing review when submission is authorized, using labeled no-private-data QA values.
  • Browser-console and failed-resource review for the agreed pages and flows.
  • Desktop, tablet, and mobile layout review at agreed representative widths.
  • Prioritized issue log with severity, affected URL, reproduction steps, expected versus observed behavior, and visual or technical evidence.
  • Handoff note separating verified, failed, and not-tested checks, with recommended owners and next actions.
  • Free 15-minute consultation for scope, access, and test-permission fit.

What you get

A bounded website QA report.

  1. Scope: Confirm the pages, priority flows, expected behavior, browsers or devices, access, and form-submission boundaries.
  2. Baseline: Record the starting URL set and the exact conditions used for the review.
  3. Inspect: Review page structure, navigation, links, redirects, console messages, and failed resources.
  4. Test: Check authorized forms and representative desktop, tablet, and mobile layouts without using private customer data.
  5. Document: Capture affected URLs, severity, reproduction steps, expected versus observed behavior, and evidence.
  6. Handoff: Separate verified, failed, and not-tested checks and recommend an owner or next action for each priority issue.

What to prepare

  • Gig ID AI-097, the primary website URL, and one agreed URL or priority-flow list.
  • Expected behavior for each priority flow and the business impact of known issues.
  • Browser, device, viewport, language, or location priorities that materially affect the review.
  • Temporary login or test access only when an authenticated path is in scope; do not send passwords through public forms or chat.
  • Explicit confirmation of whether forms may be submitted and approved labeled no-private-data QA values.
  • Any relevant release notes, known console errors, screenshots, or previous issue references.
  • One decision maker for scope boundaries, consolidated questions, and handoff ownership.

Before I start

What helps me deliver this gig without guesswork.

Business goal

Name the business goal, tools involved, what should happen, what happens now, and one real example of the broken handoff.

Safe evidence first

Start with public links, redacted screenshots, screen share, or limited collaborator access only after scope is clear.

Private access boundary

Use public links, redacted examples, or screen share first. Keep passwords, developer credentials, payment account details, customer lists, and exports out of the first message.

Protect active systems

Live leads, customers, members, tracking, reporting, support paths, ads, email, dashboards, and access rules should be checked before changes.

No unsupported promise

Gig pages do not promise rankings, revenue, ROAS, deliverability, platform approval, or generated-answer accuracy.

Leave a handoff trail

The work should leave notes on what changed, what was tested, what remains risky, and who owns each next step for documentation, repair sprint, or monthly support follow-through.

Limits

  • Production fixes, redesign, implementation, content rewriting, or deployment work.
  • Unlimited or full-site crawling beyond the agreed URL and priority-flow list.
  • Accessibility certification, legal or regulatory compliance audit, security penetration testing, or malware investigation.
  • Exhaustive device and browser-lab coverage, load testing, or performance, ranking, traffic, lead, conversion, and revenue guarantees.
  • Paid tools, apps, plugins, themes, licenses, hosting, or third-party vendor fees.
  • Destructive changes, private customer data, or live form submission without explicit written authorization.

Gig FAQ

Questions before you request this gig.

Use these answers to confirm the scope, required input, consultation path, and what happens when the request is larger than this fixed gig.

Request this gig
What is included in this gig?

One agreed website and URL or priority-flow list, page and link review, authorized form-path testing, browser-console and failed-resource review, responsive layout review, a prioritized evidence-backed issue log, and a bounded handoff note are included.

What do you need from me before starting?

Provide the website URL, agreed pages and priority flows, expected behavior, browser and device priorities, known issues, any temporary test access, and explicit permission boundaries for form submission.

Will you submit forms or change the live website?

Forms are submitted only when explicitly authorized and only with clearly labeled no-private-data QA values. This audit does not change the live website.

What is not included or needs a separate quote?

Production fixes, redesign, unlimited crawling, accessibility certification, legal compliance review, security penetration testing, paid tools, exhaustive device-lab coverage, and performance or business-outcome guarantees are not included.

Related

Compare nearby agreed-scope services.