David Dias

Create and audit JSON-LD, structured data that describes page content to search engines. Check JSON syntax, schema types, and required fields for articles, products, FAQs, and breadcrumbs, then guide validation for enhanced search results.

• Creating structured data for articles and products
• Checking FAQ and breadcrumb structured data
• Finding JSON syntax errors and missing required fields

Audit JavaScript delivered to modern browsers for unnecessary older code and compatibility patches. Confirm performance costs with measurements, then review build targets and browser-specific delivery to reduce avoidable download size and processing work.

• Investigating slow page loads
• Checking unnecessary JavaScript compatibility code
• Reviewing build targets for modern browsers

Review CSS spacing, borders, and positioning for conversion to logical properties, which follow writing direction. Check rendered layouts across screen sizes and interaction states to support right-to-left languages and vertical text.

• Adapting layouts for Arabic or Hebrew
• Replacing fixed left and right spacing in CSS
• Reviewing layouts for vertical writing

Audit URL capitalization and help standardize paths to lowercase. Review routes, internal links, and sitemaps, then check that uppercase variants permanently redirect to the lowercase address to reduce duplicate page URLs.

• Auditing uppercase letters in URL paths
• Planning lowercase URL handling for a new site
• Verifying 301 redirects for mixed-case URLs

Inspect page HTML for metadata tags placed outside the head section, where page settings belong. Identify misplaced tags and guide fixes to templates or scripts that insert them into the body.

• Checking metadata placement after CMS plugin changes
• Finding metadata inserted into the body by JavaScript
• Reviewing robots, description, OG, and canonical placement

Audit and improve `/llms.txt`, a curated starting point for AI tools browsing documentation. Check its location, the usefulness and accessibility of linked pages, and its separation from existing crawl and indexing controls.

• Audit llms.txt on a public documentation site
• Select useful API references and getting-started guides
• Check documentation links for availability

Review how tests use mocks, substitutes for external services or resources. Identify excessive mocking and missing cleanup, suggest more realistic tests, and check whether automated checks consistently catch problems and prevent regressions.

• Reviewing tests with too many mocks
• Checking mock cleanup between tests
• Improving realistic API mocks

Find resources loaded over unencrypted HTTP within HTTPS pages, a problem called mixed content. Review resource URLs and security headers, then guide HTTPS replacements and automatic request upgrades to address blocked or insecure resources.

• Auditing HTTP resources on HTTPS pages
• Checking resource URLs after an HTTPS migration
• Fixing old content with embedded HTTP URLs

Audit page URLs for long paths, deep nesting, redundant words, and unnecessary dates or dynamic values. Suggest shorter addresses and the redirects and link updates needed when changing existing URLs.

• Creating concise URL slugs from article titles
• Auditing long or deeply nested URLs
• Reviewing URL patterns in a CMS or router

Review HTML lists for incorrect child elements and nesting, then identify fixes that help screen readers, tools that read page content aloud, announce item counts and positions accurately.

• Reviewing HTML list structure
• Fixing nested lists
• Checking screen reader announcements

Audit and write page titles for search results and browser tabs. Check that each page has one descriptive title, an appropriate length, a unique wording across the site, and its main keyword near the beginning.

• Auditing title tags before publishing pages
• Finding duplicate titles across a site
• Writing titles around a main keyword

Review large tables, feeds, and lists for rendering overhead. Introduce virtualization, which renders only visible items and a small buffer, while preserving keyboard access, selection, and expected scrolling behavior.

• Investigate sluggish admin tables
• Review long search result lists
• Reduce rendering overhead in feeds

Audit slow page loads by measuring LCP, the time until the largest visible content appears. Identify bottlenecks in images, server responses, and rendering, then recommend changes supported by measurements.

• Find why a page's main content appears slowly
• Review hero image loading
• Prioritize fixes using Lighthouse measurements

Review whether interactive web elements work with keyboard navigation. Check Tab order, hidden elements, and focus traps where users cannot move away, then identify specific fixes and ways to verify behavior with browser accessibility tools or assistive technology.

• Check whether all controls are reachable with Tab
• Align keyboard focus order with the visual reading order
• Remove hidden content from the Tab sequence

Review HTTP Content-Type headers, which identify file formats, across web pages and static assets. Find mismatches that can block stylesheets or scripts, and identify server configuration changes needed to serve resources correctly.

• Investigating stylesheets or scripts that fail to load
• Auditing server settings for static assets
• Checking character encoding and nosniff headers

Audit informational pages so AI assistants can extract and understand their content. Review headings, HTML structure, content availability without JavaScript, and structured data, then suggest changes that make individual sections clearer when read on their own.

• Review pages intended for AI-generated answers
• Make headings and sections understandable on their own
• Check whether key content is available without JavaScript

Review links so their destinations are clear even without surrounding text. Identify vague wording, improve names announced by screen readers, and check keyboard behavior and download details such as file type and size.

• Replace vague link text with clear destination names
• Review links for screen reader users
• Check download links for file type and size

Check that HTML declares the correct page language and marks sections written in other languages. Find missing, empty, or invalid language tags and suggest corrections that support screen reader pronunciation, browser translation, and spell checking.

• Checking the language declared for a page
• Marking language changes in multilingual content
• Reviewing language settings for screen reader pronunciation

Audit CSS class names for inconsistency and ambiguity, then organize them using BEM, a convention that names components, their elements, and variations. Check the rendered interface across screen sizes and interaction states when reviewing changes.

• Auditing inconsistent CSS class names
• Renaming component classes using BEM
• Separating utility classes and JavaScript hooks

Audit website images and guide conversion to WebP and AVIF, formats that reduce image transfer size. Identify affected files, add fallback images, and review dimensions and loading behavior alongside the impact on initially visible content.

• Finding JPEG and PNG images to convert
• Adding WebP and AVIF sources with fallback images
• Reviewing CSS background image formats

Scan links within the same domain for the nofollow attribute, a setting used to qualify links for search engines. List affected pages, link text, and destinations, then guide removal or changes based on the intended purpose.

• Auditing nofollow attributes on internal links
• Reviewing links in navigation, headers, and footers
• Finding nofollow applied broadly by templates

Review HTML list structure so screen readers can identify lists and announce item counts. Find list items without valid containers, check custom accessibility roles, and guide fixes to markup used for navigation or styling.

• Review list markup split across components
• Fix navigation lists with invalid nesting
• Check parent roles for custom lists

Audit JavaScript page redirects, confirm their impact on loading time with performance measurements, and identify where server-side 301 or 302 redirects can replace them. Get specific findings and an explanation of loading and search indexing concerns.

• Investigating slow loads caused by page redirects
• Reviewing redirects that use window.location
• Planning server-side 301 or 302 redirects

Create and audit meta descriptions, the short page summaries used in search results. Find missing, duplicate, or unsuitable descriptions and write distinct summaries that accurately explain each page’s content and value.

• Writing descriptions for new pages
• Finding missing or duplicate descriptions
• Reviewing description length and HTML markup