Issue Selection & Safety

Align organizes detected issues into four categories. Each category represents a different aspect of your site's SEO and GEO health:

• Metadata — Issues with title tags, meta descriptions, and Open Graph tags. These are the most common issues and typically the easiest to fix.
• Schema — Missing or invalid JSON-LD structured data. Schema helps search engines and AI platforms understand the content and context of your pages.
• AI Readiness — Issues related to your llms.txt file, which tells AI engines how to interpret and cite your content.
• Authority — Topical gaps where your site lacks content on important subjects in your domain. These are identified by the Authority Map analysis.

The action panel on the right side of the dashboard displays all fixable issues after a scan. Each issue has a checkbox that you can toggle to include or exclude it from a PR.

Selection controls:

• Individual checkbox — Click the checkbox next to any single issue to toggle it.
• Select all — Click the "Select All" button to select every fixable issue across all categories.
• Select by category — Click a category header checkbox to select all issues in that category.
• Deselect all — Click "Deselect All" to clear all selections and start over.

Understanding what Align changes for each fix type helps you make informed decisions about which issues to include in your PR:

• Metadata fixes — Updates your HTML to add or improve the <title> tag, the <meta name="description"> tag, and Open Graph meta tags like og:title and og:description.
• Schema fixes — Adds or updates JSON-LD structured data in your pages. This includes adding <script type="application/ld+json"> blocks with the appropriate schema types for your content.
• AI Readiness fixes — Creates or updates the llms.txt file at the root of your site. This file provides structured information to AI crawlers about your content.
• Authority fixes — Suggests content additions to fill topic gaps. These are typically new sections or paragraphs that strengthen your topical coverage in areas where competitors have content but you do not.

The safety score is a percentage calculated based on the complexity and confidence of the selected fixes. It helps you gauge how risky the changes are before creating a PR.

The score considers factors like the type of change (adding vs. modifying), the number of files affected, and the complexity of the generated code.

A safety score of 80% or above indicates simple, low-risk changes. These are typically:

• Adding missing meta description tags
• Filling in empty title tags
• Adding Open Graph tags that do not exist yet
• Creating a new, straightforward JSON-LD block

High-safety changes are predictable and unlikely to cause issues. You can generally merge these with confidence after a quick review.

A safety score between 50% and 80% indicates moderate changes that deserve closer review. These often include:

• Adding complex schema types with multiple nested properties
• Modifying existing meta tags that already have content
• Making changes across multiple files simultaneously

Medium-safety changes are usually correct, but previewing the diff before creating the PR is recommended.

A safety score below 50% means the changes are more complex and should be reviewed carefully. Scenarios that produce lower scores include:

• Large-scale content additions for authority gaps
• Complex schema modifications on pages with existing structured data
• Fixes that touch many files across the repository

Lower-safety changes are not necessarily wrong, but they require thorough review. Always preview the diff and consider testing locally before merging.

Regardless of the safety score, you should always preview the diff before creating a PR. The preview shows the exact changes that will be made to each file in your repository.

When reviewing the preview, check for:

• Correct file paths — are the changes targeting the right pages?
• Content accuracy — are generated descriptions relevant to the page content?
• Schema correctness — does the JSON-LD use the right schema types?
• No duplicate tags — are new tags being added without duplicating existing ones?

If something looks off, deselect the problematic issue and create the PR with only the changes you are confident about.