Want to know exactly what happens under the hood when an on-page SEO tool flags a problem? I’ll walk you through the technical processes, data flows, and decision rules that power modern on-page optimization tools. This article focuses on the mechanics — crawlers, parsers, scoring algorithms, and integrations — so you can evaluate tools like an engineer instead of a marketer glancing at a dashboard.
What Are On-Page Optimization Tools and Why They Matter
Definition and scope
On-page optimization tools inspect individual pages and report issues that impact search visibility and user experience. They check meta tags, heading structure, content relevance, images, structured data, canonicalization, and technical signals like page speed. Think of them as automated auditors that combine HTML parsing, semantic analysis, and performance testing to produce actionable recommendations.
Why take a technical deep dive?
Marketers want quick fixes; developers need predictable outputs. Understanding the architecture and heuristics behind these tools helps you interpret false positives, optimize automation, and avoid changes that break functionality. When you know how a tool tokenizes text, scores relevance, or measures Core Web Vitals, you make smarter, safer decisions.
Core Components Measured by On-Page Tools
Title tags and meta descriptions
Tools extract </strong> and meta description values, calculate pixel widths, and detect truncation based on SERP rendering rules. They often simulate different device viewports so they can flag titles that will be clipped on mobile but appear full on desktop. A key technical detail: many modern tools calculate effective length in pixels using font metrics rather than character count, which reduces false alerts.</p>
<h3>Headings, semantic structure, and content hierarchy</h3>
<p>On-page analyzers parse heading tag order (H1 → H2 → H3), evaluate depth, and detect accessibility issues. They typically build a DOM-based tree to check whether headings follow logical hierarchy and whether ARIA roles or hidden content distort the sequence. That DOM snapshot is crucial for tools to replicate what bots and screen readers see.</p><div class="my-4 text-center"><img src="https://webbloggin.online/admin/uploads/articles/ai_fallback_6944fedb9fe79.jpg" class="img-fluid rounded shadow-sm" alt="What Are On-Page Optimization Tools and Why They Matter"></div>
<h3>URL, canonical tags, and indexability</h3>
<p>Tools verify canonical links, rel="next"/"prev", and noindex directives while resolving HTTP redirects. They often fetch the raw HTTP headers and HTML in parallel to compare what the server delivers versus what the browser-rendered DOM shows. This dual-fetch approach reveals server-side misconfigurations that break canonical strategies.</p>
<h2>Tool Types and Their Architectures</h2>
<h3>Crawler-based site auditors</h3>
<p>Crawler tools emulate search engine bots, following internal links, respecting robots rules, and building a site graph. They schedule requests, manage rate limits, and parse robots.txt before crawling. For large sites, they use incremental crawls and diffing to highlight new issues since the last run, which conserves bandwidth and accelerates actionable reporting.</p>
<h3>Browser-based renderers and extensions</h3>
<p>Some on-page tools run a headless browser to capture the fully rendered DOM, execute JavaScript, and measure layout shifts. That matters when a site builds headings client-side or injects structured data with scripts. Headless rendering finds issues crawler-only approaches miss, such as content hidden by JavaScript or dynamically injected canonical tags.</p>
<h3>API-driven platforms and modular services</h3>
<p>APIs let development teams integrate specific checks into build pipelines or CI systems. For example, a content pipeline can call an API to validate metadata before publishing. This modular approach turns ad-hoc audits into pre-commit gates, reducing regressions and ensuring continuous compliance with on-page best practices.</p>
<h2>How Tools Analyze Content Semantics</h2>
<h3>Natural Language Processing and topical relevance</h3>
<p>Modern tools go beyond keyword frequency and use NLP to assess topical coverage, entities, and semantic similarity. They employ tokenization, stemming, named entity recognition, and embedding models to compare a page’s content against a target intent or competitor set. That’s why some audits will say a page “lacks topical depth” rather than merely “missing keyword X.”</p><div class="my-4 text-center"><img src="https://webbloggin.online/admin/uploads/articles/ai_fallback_6944fedea818f.jpg" class="img-fluid rounded shadow-sm" alt="Core Components Measured by On-Page Tools"></div>
<h3>Keyword density versus contextual use</h3>
<p>Keyword Density Checker-style metrics still appear in many tools, but smarter platforms weigh context over raw counts. They use co-occurrence matrices and proximity analysis to detect whether related terms appear naturally, not just stuffed. That reduces noisy recommendations and aligns optimization with modern semantic search models.</p>
<h3>LSI and latent semantics in scoring</h3>
<p>Tools calculate LSI-like signals by building vector representations of text and measuring cosine similarity to a topical centroid. In practical terms, that means a page covering multiple subtopics around a subject scores higher for relevance even if it doesn't repeat the primary keyword excessively. The result: more nuanced suggestions like “add subtopic sections” instead of “add keyword more.”</p>
<h2>Technical Signals: Performance, Mobile, and Core Web Vitals</h2>
<h3>Measuring page speed and resource performance</h3>
<p>On-page tools collect waterfall charts, measure TTFB, and analyze critical rendering paths. They simulate network conditions with throttling and parse response headers to detect caching and compression misconfigurations. When tools report slow resources, they usually link the complaint to a specific asset and suggest fixes like Brotli/Gzip compression, HTTP/2, or preload directives.</p>
<h3>Core Web Vitals: LCP, CLS, and FID/INP</h3>
<p>Tools instrument pages to measure Largest Contentful Paint, Cumulative Layout Shift, and interaction latency under simulated or real-user conditions. They aggregate lab and field metrics, explaining how server timing, render-blocking CSS, or non-deterministic third-party scripts create poor scores. Knowing whether an issue is repeatable in headless tests or appears only in RUM data helps prioritize fixes.</p>
<h3>Mobile-specific audits and responsive behavior</h3>
<p>Mobile audits verify viewport meta tags, touch target sizes, and layout breakpoints. They also check resource loading strategies like responsive images and adaptive code paths. Tools that combine visual diffing with DOM snapshots can flag elements that overlap on small screens or content hidden behind off-canvas navs.</p><div class="my-4 text-center"><img src="https://webbloggin.online/admin/uploads/articles/ai_fallback_6944fee16c14d.jpg" class="img-fluid rounded shadow-sm" alt="Tool Types and Their Architectures"></div>
<h2>Structured Data and Schema Markup Validation</h2>
<h3>Parsing JSON-LD, Microdata, and RDFa</h3>
<p>Tools detect structured data formats, parse JSON-LD blocks, and validate schema types against known vocabularies. They often use strict schema validators that report missing required properties or incorrect types. For publishers using programmatic templates, these validators can run as part of a CI job to stop invalid markup from reaching production.</p>
<h3>Common schema issues and edge cases</h3>
<p>Incorrectly nested objects, duplicated schema for the same entity, or mismatched URLs between canonical tags and schema often trigger tool warnings. Tools that cross-check schema against the visible content and canonicalization reduce false positives by ensuring the structured data corresponds to the page’s primary entity.</p>
<h2>Image and Media Optimization</h2>
<h3>Alt text, dimensions, and compression</h3>
<p>On-page tools flag missing alt attributes, non-declared image dimensions, and oversized files that bloat load time. They analyze format choices (JPEG vs WebP vs AVIF) and recommend conversions and quality targets. For sites with many media assets, automation scripts can batch-optimize images and update templates to serve modern formats with fallbacks.</p>
<h3>Responsive images and lazy loading</h3>
<p>Tools verify srcset usage, picture elements, and lazy-loading patterns to ensure the browser receives appropriately sized assets for each viewport. They simulate slow connections to confirm lazy loading triggers correctly. If you’re experimenting with lazy-load for third-party widgets, check out implementation patterns such as those discussed in <a href='article/how-to-lazy-load-recaptcha-optimizing-website-performance'>How to Lazy Load reCAPTCHA? Optimizing Website Performance</a>.</p>
<h2>Accessibility and Content Quality Checks</h2>
<h3>Automated accessibility scanning</h3>
<p>On-page tools include contrast checks, keyboard navigation simulations, and ARIA attribute audits. They surface accessibility violations that also impact SEO, like hidden headings or images without textual alternatives. Prioritizing fixes that help both users and search engines gives you double value from accessibility work.</p><div class="my-4 text-center"><img src="https://webbloggin.online/admin/uploads/articles/ai_fallback_6944fee42d201.jpg" class="img-fluid rounded shadow-sm" alt="How Tools Analyze Content Semantics"></div>
<h3>Readability, duplicate content, and canonicalization</h3>
<p>Tools analyze reading grade scores, internal duplication, and near-duplicate detection using shingling or fuzzy hashing. They highlight candidate canonical sources and duplicate clusters so you can consolidate signals and avoid cannibalization. That prevents situations where thin, duplicated pages compete with your intended canonical content.</p>
<h2>From Report to Fix: Integrating Tools into Your Workflow</h2>
<h3>Automation and CI/CD integration</h3>
<p>Turn audits into pre-deploy gates by integrating API-driven checks into your build pipeline. A failing metadata validator can block a merge request and attach a ticket to the author with a clear remediation path. That reduces hotfix churn and enforces site-wide consistency across teams handling content and code.</p>
<h3>Ticketing, triage, and remediation strategies</h3>
<p>Not every issue has equal impact. Use data-driven prioritization: combine traffic, conversion, and crawl frequency with the tool’s severity score to create a remediation roadmap. For large sites, run sampling audits and prioritize fixes that affect high-traffic templates rather than low-value pages.</p>
<h3>Monitoring and regression detection</h3>
<p>Set up scheduled crawls and RUM integration to detect regressions after releases. Tools that offer diff reports and trend lines help you see whether an optimization improved LCP or unintentionally broke structured data. Continuous monitoring catches problems early so they don’t compound into ranking losses.</p>
<h2>Choosing the Right On-Page Tool: Criteria and Trade-offs</h2>
<h3>Feature parity vs. integration capabilities</h3>
<p>Some tools offer rich feature sets with headless rendering and structured data testing, while others specialize in fast, lightweight audits you can run in CI. Choose a tool that aligns with your stack: heavy server-rendered sites benefit more from headless crawlers, single-page apps need robust JavaScript rendering, and content-heavy publishers should prioritize semantic analysis.</p><div class="my-4 text-center"><img src="https://webbloggin.online/admin/uploads/articles/ai_fallback_6944fee7a91e3.jpg" class="img-fluid rounded shadow-sm" alt="Technical Signals: Performance, Mobile, and Core Web Vitals"></div>
<h3>Cost, scalability, and data ownership</h3>
<p>Consider API rate limits, data export options, and whether you can self-host crawlers for privacy or performance reasons. Large enterprises often prefer platforms that let them run private crawlers and retain raw crawl data, while smaller teams may opt for SaaS that reduces maintenance burden.</p>
<h3>Additional resources and tools to pair with on-page audits</h3>
<p>For metadata generation and verification, pairing an on-page auditor with a meta tag tool speeds up remediation. If you want a deep metadata perspective, check <a href='article/meta-tag-generator-tool-trends-driving-smarter-metadata-and-what-comes-next'>Meta Tag Generator Tool: Trends Driving Smarter Metadata and What Comes Next</a>. For broad site health and prioritized fixes, use a site analyzer that connects page-level problems to site architecture, like <a href='article/seo-website-analyzer-a-strategic-practical-guide-to-fixing-what-holds-your-site-back'>SEO Website Analyzer: A Strategic, Practical Guide to Fixing What Holds Your Site Back</a>. If keyword density comes up as a concern during content audits, consult tools such as the <a href='article/keyword-density-checker-which-tool-actually-helps-your-seo-comparative-review-pros-cons'>Keyword Density Checker</a> analysis to avoid chasing misleading metrics.</p>
<h2>Real-World Example: Fixing a Slow Product Page</h2>
<h3>Step-by-step breakdown</h3>
<p>Imagine a product page with high impressions but low conversions and slow LCP. Start with a crawler audit to identify resource sizes and unused CSS. Then run a headless render to confirm the largest contentful element and measure LCP under mobile throttling. Next, optimize images to WebP, implement critical CSS inlining for above-the-fold content, and lazy-load below-the-fold scripts. After deploying, schedule a follow-up crawl and verify improvement in both lab tests and RUM metrics.</p>
<h3>Why the technical approach pays off</h3>
<p>Prioritizing changes based on traceroutes and resource waterfall analysis prevents wasted effort on low-impact tweaks like changing meta descriptions. A technical workflow focuses on measurable improvements: reduced bytes, faster render time, and fewer layout shifts, leading to better user experience and stronger SEO signals.</p>
<h2>Common Pitfalls and How to Avoid Them</h2>
<h3>Over-reliance on single metrics</h3>
<p>Trusting a single score or indicator can mislead teams into chasing vanity metrics. Combine lab and field data, and correlate SEO performance with business KPIs like organic conversions and page revenue. That gives you a practical sense of whether a fix matters.</p>
<h3>Interpreting false positives</h3>
<p>Automated tools sometimes flag issues that aren’t real problems for your setup — for example, intentionally deferred canonical tags or client-side injected content that’s validated server-side. Validate tool findings with manual checks and server logs before applying sweeping changes.</p>
<h3>Keeping checks relevant as technology evolves</h3>
<p>Search engines change behavior. Maintain a ruleset cadence, update parsing logic for new HTML patterns, and re-evaluate heuristics for metrics like LCP and CLS as browser engines evolve. Treat your audit tooling like any other software component that needs versioning and maintenance.</p>
<h2>Conclusion: Turning Tool Output into Measurable Wins</h2>
<p>On-page optimization tools are powerful, but their value depends on understanding how they work. When you know how crawlers fetch pages, how renderers capture DOMs, and how semantic scoring works, you can separate real problems from noise. Start by integrating targeted checks into your CI pipeline, prioritize fixes by traffic and technical impact, and use both lab and real-user data to measure success. Want help choosing a toolchain or building custom checks for your stack? Reach out and I’ll help map a technical roadmap tailored to your site’s architecture.</p>
<p><strong>Call to action:</strong> Run a technical audit this week, pick the top three fixes by impact, and turn them into deployable tickets. If you’d like sample scripts or a checklist to integrate audits into your CI, let me know and I’ll share a starter pack.</p></p> </div>
<hr class="my-5">
<div class="text-center">
<h5 class="fw-bold mb-3">Share this article</h5>
<div class="d-flex justify-content-center gap-2">
<a href="https://www.facebook.com/sharer/sharer.php?u=http%3A%2F%2Fwebbloggin.online%2Farticle.php%3Fslug%3Don-page-optimization-tools-a-technical-deep-dive-every-seo-engineer-needs" target="_blank" class="btn btn-outline-primary btn-sm rounded-pill px-3"><i class="fab fa-facebook-f me-2"></i> Facebook</a>
<a href="https://twitter.com/intent/tweet?url=http%3A%2F%2Fwebbloggin.online%2Farticle.php%3Fslug%3Don-page-optimization-tools-a-technical-deep-dive-every-seo-engineer-needs&text=On-Page+Optimization+Tools%3A+A+Technical+Deep+Dive+Every+SEO+Engineer+Needs" target="_blank" class="btn btn-outline-info btn-sm rounded-pill px-3"><i class="fab fa-twitter me-2"></i> Twitter</a>
<a href="https://wa.me/?text=On-Page+Optimization+Tools%3A+A+Technical+Deep+Dive+Every+SEO+Engineer+Needs+http%3A%2F%2Fwebbloggin.online%2Farticle.php%3Fslug%3Don-page-optimization-tools-a-technical-deep-dive-every-seo-engineer-needs" target="_blank" class="btn btn-outline-success btn-sm rounded-pill px-3"><i class="fab fa-whatsapp me-2"></i> WhatsApp</a>
</div>
</div>
</div>
</div>
</div>
<footer class="footer bg-white pt-5 pb-3 mt-5 border-top">
<div class="container">
<!-- Footer Ad -->
<div class="row gx-4">
<!-- About Column -->
<div class="col-lg-3 col-md-6 mb-4">
<h5 class="fw-bold mb-3">Webbloggin WebTools</h5>
<p class="text-muted small">Webbloggin WebTools is your free, all-in-one platform for SEO, YouTube analytics, and webmaster tools to track, optimize, and grow your online presence.</p>
<div class="social-links mt-3">
<a href="#" class="text-muted me-3" aria-label="Facebook"><i class="fab fa-facebook fa-lg"></i></a>
<a href="#" class="text-muted me-3" aria-label="Twitter"><i class="fab fa-twitter fa-lg"></i></a>
<a href="#" class="text-muted me-3" aria-label="Instagram"><i class="fab fa-instagram fa-lg"></i></a>
</div>
<div class="footer-intro mt-4 small text-muted border-top pt-3">
<h6 class="fw-bold mb-2 text-dark">About Us</h6>
OneKit WebTools is your free, all-in-one platform for SEO, YouTube analytics, and webmaster tools to track, optimize, and grow your online presence.
</div>
</div>
<!-- Tools Category Column -->
<div class="col-lg-2 col-md-6 mb-4">
<h6 class="fw-bold mb-3">Tools Category</h6>
<ul class="list-unstyled small">
<li class="mb-2">
<a href="/category/text-tools" class="text-muted text-decoration-none">
Text Tools </a>
</li>
<li class="mb-2">
<a href="/category/youtube-tools" class="text-muted text-decoration-none">
YouTube Tools </a>
</li>
<li class="mb-2">
<a href="/category/seo-tools" class="text-muted text-decoration-none">
SEO Tools </a>
</li>
<li class="mb-2">
<a href="/category/domain-ip-tools" class="text-muted text-decoration-none">
Domain & IP Tools </a>
</li>
<li class="mb-2">
<a href="/category/website-management-tools" class="text-muted text-decoration-none">
Website Management Tools </a>
</li>
<li class="mb-2">
<a href="/category/web-development-tools" class="text-muted text-decoration-none">
Web Development Tools </a>
</li>
<li class="mb-2">
<a href="/category/image-editing-tools" class="text-muted text-decoration-none">
Image Editing Tools </a>
</li>
<li class="mb-2">
<a href="/category/online-calculators" class="text-muted text-decoration-none">
Online Calculators </a>
</li>
<li class="mb-2">
<a href="/category/binary-converter-tools" class="text-muted text-decoration-none">
Binary Converter Tools </a>
</li>
<li class="mb-2">
<a href="/category/unit-converter-tools" class="text-muted text-decoration-none">
Unit Converter Tools </a>
</li>
<li class="mb-2">
<a href="/category/miscellaneous-tools" class="text-muted text-decoration-none">
Miscellaneous Tools </a>
</li>
</ul>
</div>
<!-- Legal Column -->
<div class="col-lg-2 col-md-6 mb-4">
<h6 class="fw-bold mb-3">Legal</h6>
<ul class="list-unstyled small">
<li class="mb-2">
<a href="/page/about-us" class="text-muted text-decoration-none">
About Us </a>
</li>
<li class="mb-2">
<a href="/page/contact-us" class="text-muted text-decoration-none">
Contact Us </a>
</li>
<li class="mb-2">
<a href="/page/disclaimer" class="text-muted text-decoration-none">
Disclaimer </a>
</li>
<li class="mb-2">
<a href="/page/privacy-policy" class="text-muted text-decoration-none">
Privacy Policy </a>
</li>
<li class="mb-2">
<a href="/page/terms-of-services" class="text-muted text-decoration-none">
Terms of Services </a>
</li>
</ul>
</div>
<!-- Our YouTube Tools Column -->
<div class="col-lg-2 col-md-6 mb-4">
<h6 class="fw-bold mb-3">Our YouTube Tools</h6>
<ul class="list-unstyled small">
<li class="mb-2">
<a href="/youtube-tag-extractor" class="text-muted text-decoration-none">
YouTube Tag Extractor </a>
</li>
<li class="mb-2">
<a href="/youtube-title-generator" class="text-muted text-decoration-none">
YouTube Title Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-money-calculator" class="text-muted text-decoration-none">
YouTube Money Calculator </a>
</li>
<li class="mb-2">
<a href="/youtube-hashtag-extractor" class="text-muted text-decoration-none">
YouTube Hashtag Extractor </a>
</li>
<li class="mb-2">
<a href="/youtube-thumbnail-downloader" class="text-muted text-decoration-none">
YouTube Thumbnail Downloader </a>
</li>
<li class="mb-2">
<a href="/youtube-tag-generator" class="text-muted text-decoration-none">
YouTube Tag Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-region-restriction-checker" class="text-muted text-decoration-none">
YouTube Region Restriction Checker </a>
</li>
<li class="mb-2">
<a href="/youtube-title-length-checker" class="text-muted text-decoration-none">
YouTube Title Length Checker </a>
</li>
<li class="mb-2">
<a href="/youtube-embed-code-generator" class="text-muted text-decoration-none">
YouTube Embed Code Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-title-extractor" class="text-muted text-decoration-none">
YouTube Title Extractor </a>
</li>
<li class="mb-2">
<a href="/youtube-hashtag-generator" class="text-muted text-decoration-none">
YouTube Hashtag Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-banner-downloader" class="text-muted text-decoration-none">
YouTube Channel Banner Downloader </a>
</li>
<li class="mb-2">
<a href="/youtube-subscribe-link-generator" class="text-muted text-decoration-none">
YouTube Subscribe Link Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-description-generator" class="text-muted text-decoration-none">
YouTube Description Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-id-extractor" class="text-muted text-decoration-none">
YouTube Channel ID Extractor </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-finder" class="text-muted text-decoration-none">
YouTube Channel Finder </a>
</li>
<li class="mb-2">
<a href="/youtube-comment-picker" class="text-muted text-decoration-none">
YouTube Comment Picker </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-age-checker" class="text-muted text-decoration-none">
YouTube Channel Age Checker </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-statistics" class="text-muted text-decoration-none">
YouTube Channel Statistics </a>
</li>
<li class="mb-2">
<a href="/youtube-description-extractor" class="text-muted text-decoration-none">
YouTube Description Extractor </a>
</li>
<li class="mb-2">
<a href="/youtube-channel-logo-downloader" class="text-muted text-decoration-none">
YouTube Channel Logo Downloader </a>
</li>
<li class="mb-2">
<a href="/youtube-video-statistics" class="text-muted text-decoration-none">
YouTube Video Statistics </a>
</li>
<li class="mb-2">
<a href="/youtube-timestamp-link-generator" class="text-muted text-decoration-none">
YouTube Timestamp Link Generator </a>
</li>
<li class="mb-2">
<a href="/youtube-video-title-capitalizer" class="text-muted text-decoration-none">
Youtube Video Title Capitalizer </a>
</li>
<li class="mb-2">
<a href="/youtube-views-ratio-calculator" class="text-muted text-decoration-none">
YouTube Views Ratio Calculator </a>
</li>
<li class="mb-2">
<a href="/youtube-video-count-checker" class="text-muted text-decoration-none">
YouTube Video Count Checker </a>
</li>
</ul>
</div>
<!-- Newsletter Column -->
<div class="col-lg-3 col-md-6 mb-4">
<h6 class="fw-bold mb-3">Newsletter</h6>
<p class="small text-muted">Subscribe to our newsletter for updates.</p>
<form action="#" method="post" class="mt-2" onsubmit="return false;">
<div class="input-group">
<input type="email" class="form-control form-control-sm" placeholder="Your email" required>
<button class="btn btn-primary btn-sm" type="submit">Subscribe</button>
</div>
</form>
</div>
</div>
<hr class="my-4">
<div class="row align-items-center">
<div class="col-md-6 text-center text-md-start">
<p class="small text-muted mb-0">© 2025 Webbloggin WebTools. All rights reserved.</p>
</div>
</div>
</div>
</footer>
<!-- Bootstrap JS -->
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.0/dist/js/bootstrap.bundle.min.js"></script>
<!-- Custom JS -->
<script src="https://webbloggin.online/assets/js/main.js"></script>
<script>
// Simple search filter with error checking
const searchBox = document.getElementById('toolSearch');
if (searchBox) {
searchBox.addEventListener('keyup', function() {
let filter = this.value.toLowerCase();
// Target the new tool card class
let tools = document.querySelectorAll('.tool-card');
tools.forEach(tool => {
// Target the title inside tool-title span
let titleElement = tool.querySelector('.tool-title span');
if (titleElement) {
let title = titleElement.innerText.toLowerCase();
// The tool-card is inside an <a> tag which is inside the col div
// Structure: col -> a -> tool-card
let container = tool.closest('.col-12, .col-sm-6, .col-md-4, .col-lg-3');
if (container) {
container.style.display = title.includes(filter) ? '' : 'none';
}
}
});
});
}
</script>
</body>
</html>
