Aegisify Link Product Guide

Version 1.2
Updated July 10, 2026
Product: Aegisify Link for WordPress

Publication and validation notice: This guide was rebuilt from a static review of the Aegisify Link 1.2 package and current Aegisify public pages. It separates verified capabilities from workflows that require correction or production validation. Complete the acceptance checklist in this guide before enabling automated link creation, broad content replacement, conversion tracking, or AI-assisted recommendations on a live site.

1. Product Overview

Aegisify Link helps WordPress administrators create, organize, monitor, and measure internal and outbound links from one operational workspace. It combines automatic keyword linking, content suggestions, managed shortlinks, campaign grouping, link-health checks, click analytics, conversion markers, bulk workflows, WooCommerce-aware automation, a configurable word cloud, CSV transfer tools, and optional AI-assisted recommendations.

The product is designed for site owners, agencies, ecommerce teams, content publishers, and technical administrators that need more control than manually editing links across individual posts and pages. Its strongest value is not simply adding links. It is creating a reviewable workflow for defining destinations, applying consistent link behavior, identifying broken destinations, measuring engagement, and maintaining link policy over time.

Aegisify Link should be positioned as a WordPress link-operations and intelligence layer—not as a ranking guarantee, a replacement for editorial review, or proof that every click represents a human visitor. Search performance still depends on content quality, architecture, crawlability, relevance, user experience, and broader search-engine systems.

2. What This Guide Covers

This guide explains the reviewed 1.2 administration experience:

• Dashboard and recent click visibility
• Linking Assistant and Smart Links
• Internal-link recommendations
• Word Cloud shortcode and content extraction
• Managed shortlinks
• Redirect status codes
• Link expiration and 410 responses
• UTM parameters and campaign grouping
• Device and optional country targeting
• Click, referrer, device, browser, country, and conversion analytics
• Link-health checks
• WooCommerce-aware automation
• Bulk creation and maintenance
• CSV import and export
• AI-assisted recommendations
• Privacy, tracking, retention, and credential considerations
• License state and optional free-install registration
• Operational runbooks, troubleshooting, and acceptance testing

3. System Requirements

Before deployment, confirm rewrite behavior, page-cache and CDN interaction, object caching, outbound HTTP access, WP-Cron reliability, privacy requirements, administrator permissions, ecommerce workflows, and the active Aegisify license.

4. Important Operating Principles

4.1 Use editorially meaningful anchor text

Internal links should help a reader understand the destination. Use concise, descriptive anchor text that reflects the linked page rather than repeating a broad keyword everywhere.

4.2 Automate narrowly

Automatic linking can save time, but an unrestricted rule can over-link content, place links in inappropriate context, or create a poor reading experience. Begin with a small set of high-confidence terms and review representative pages.

4.3 Redirects are operational assets

A managed shortlink can affect campaigns, advertising, email, product pages, QR codes, and external publications. Protect slugs, destination URLs, status codes, expiration settings, and campaign ownership through change control.

4.4 Analytics require context

Click counts can include bots, social-preview fetches, monitoring systems, repeated visitors, and automated traffic. Use analytics as operational evidence, not as a guaranteed count of unique human prospects.

4.5 Health checks do not validate business meaning

A 200 or 301 response can still lead to the wrong page, a soft 404, an expired offer, a login wall, or an irrelevant destination. Combine automated health checks with campaign and content-owner review.

4.6 Respect privacy and retention

The reviewed analytics workflow can store referrer, user-agent, campaign identifiers, conversion state, device and browser classifications, hashed IP data, and a persistent reference token. Publish an appropriate privacy notice, minimize retention, and restrict access.

5. Administration Navigation

The reviewed package organizes Aegisify Link into these primary areas.

Links Management views

The Links Management workspace includes:

• Setup Wizard
• Manage
• Bulk
• Link Groups
• Analytics
• Import/Export

Version 1.2 advisory: The reviewed package is missing the expected Tools & License page file. Until a corrected build is installed, that tab can display a missing-page message instead of the intended license and registration interface.

6. What Is New or Materially Expanded in Version 1.2

The live guide still identifies version 1.1.18. Version 1.2 represents a broader link-operations platform with expanded automation, campaigns, health monitoring, commerce workflows, analytics, and recommendations.

Managed link operations

Administrators can create shortlinks with configurable slugs, destination URLs, redirect status, nofollow or sponsored metadata, UTM values, expiration rules, click thresholds, groups, and tags.

Campaign intelligence

Campaign groups can define shared UTM defaults and provide roll-up views for clicks, broken destinations, and top-performing managed links.

Scheduled link health

A daily background process checks links in controlled batches and records response status, failures, and last-check evidence. Administrators can also trigger manual checks.

WooCommerce-aware automation

The package can detect WooCommerce and create managed links for products and product categories according to configured templates and status controls.

Expanded analytics

The analytics workspace includes totals, unique-click indicators, time-series views, top links, referrers, countries, devices, browsers, conversions, campaign fields, and ecommerce-oriented reports.

Optional AI recommendations

Administrators can opt in to sending selected content context to a configured AI endpoint. The response can be stored as recommendation and issue data for review.

Word Cloud and shortcode output

The [aegislink_keywords_block] shortcode can generate a keyword cloud from page or post content, including selected page-builder and rendered-content fallbacks.

7. Quick Start

7.1 Establish a controlled baseline

1. Install and activate Aegisify Link 1.2.
2. Save WordPress permalinks.
3. Open Aegisify Link → Dashboard.
4. Review the active license and available modules.
5. Create one managed shortlink.
6. Test its redirect in a private browser window.
7. Create one narrowly scoped Smart Link.
8. Review several representative pages.
9. Run one manual health check.
10. Confirm that clicks and health evidence appear as expected.
11. Document the owner and purpose of the link.
12. Enable scheduled or automated workflows only after the manual path is accepted.

7.2 Recommended initial posture

8. Dashboard

The Dashboard provides a high-level view of link activity and shortcuts into primary workflows.

Reviewed dashboard concepts include:

• Recent click activity
• Managed-link totals
• Broken-link or health indicators
• Shortcuts to creation and analysis
• A WordPress dashboard widget showing recent click records

Recommended review

During rollout, compare dashboard counts with expected test activity. A click that does not appear can indicate caching, route ownership, blocked requests, or a tracking configuration issue. Unexpectedly high counts can indicate bots, social previews, or monitoring traffic.

9. Linking Assistant

The Linking Assistant helps administrators define reusable internal-link behavior and identify relevant content relationships.

Smart Links

A Smart Link maps a configured keyword to a destination URL. During eligible WordPress content rendering, Aegisify Link can replace matching text with an anchor element.

The reviewed implementation processes:

• Main post content
• Excerpts
• Selected widget output
• Elementor-rendered content

It avoids replacement inside existing links and selected code-oriented elements such as code, pre, script, and style.

Important version 1.2 limitations

• Reviewed Smart Link matching is designed around one-word keywords rather than arbitrary multi-word phrases.
• A matching keyword can be linked more than once in eligible content.
• The reviewed workflow does not expose a clear “first occurrence only” or per-page link-count setting.
• Smart Link output uses noopener behavior but does not apply the same nofollow or sponsored controls used by managed shortlinks.

Safe Smart Link workflow

1. Select a distinctive term.
2. Confirm that the destination is canonical and indexable.
3. Review existing uses of the term.
4. Create the rule.
5. Test posts, pages, widgets, and page-builder content.
6. Review mobile output and accessibility.
7. Check that the link does not appear inside headings or contexts where it changes meaning.
8. Monitor over-linking and reader complaints.
9. Disable or narrow the rule when the term is ambiguous.

10. Internal-Link Suggestions

The suggestion engine can use page titles, categories, tags, and WordPress content relationships to find possible destinations.

Suggestions should be treated as editorial candidates. Before adding a link, confirm:

• The destination is relevant.
• The anchor describes the destination.
• The page is canonical and current.
• The link improves navigation or understanding.
• The content is not already over-linked.
• The link does not create a circular or misleading path.

Version 1.2 validation advisory

The reviewed suggestion provider and administration display use different field names for suggestion records. This can cause empty anchor or explanation fields in the interface. Use suggestions only after confirming that the corrected build displays complete recommendation data.

11. Word Cloud

The Word Cloud provides a visual keyword block through:

[aegislink_keywords_block]

The feature can extract visible text from several sources:

• Standard post content
• Rendered content
• A loopback fetch of the public page
• Elementor metadata
• Fusion or page-builder metadata
• Visible HTML text

Configuration concepts

Administrators can control:

• Section title
• Number of displayed words
• Minimum and maximum visual size
• Stop words and filtering behavior
• Display style
• Footer branding behavior

Operational cautions

The loopback content fetch can depend on hosting, DNS, caching, authentication, and firewall behavior. Results are cached for a limited period, but the first generation can add latency.

In the reviewed 1.2 build, the footer-branding option is not reliably respected when settings are saved, and the fallback error output can still display a footer link. Verify the deployed behavior before promising that branding can be disabled.

Word Cloud review

• Check the words for relevance.
• Remove private, sensitive, or misleading terms.
• Confirm the block does not compete with important calls to action.
• Test mobile wrapping.
• Confirm that the page does not make a slow loopback request on every view.
• Re-test after page-builder or cache changes.

12. Managed Shortlinks

Managed shortlinks use a configurable path, such as:

/go/example

Each record can include:

• Destination URL
• Slug
• Redirect code
• Status
• Title and notes
• Nofollow and sponsored metadata
• UTM parameters
• Start and expiration dates
• Click-limit expiration
• Group and tag classification
• Device or optional country targeting
• QR code access
• Click and conversion evidence

Redirect codes

Choose the code based on the operational intent, not merely convenience.

Expiration

A link can expire by:

• Date
• Click count
• Administrative status

An expired link can return 410 Gone. Define an owner and replacement experience for customer-facing campaigns before expiration.

Slug governance

Use short, readable, non-sensitive slugs. Avoid embedding customer data, internal ticket numbers, credentials, or unreleased campaign information in public paths.

13. Device and Country Targeting

The package includes device classification and an extension point for country-based routing.

Device targeting

Device behavior is inferred primarily from the user-agent string. User agents can be absent, misleading, or changed by privacy tools.

Country targeting

Country routing depends on another component supplying country information through the Aegisify filter. The reviewed package does not include a complete built-in GeoIP provider.

When using country codes, use the code format expected by the active provider. Validate the United Kingdom as GB when ISO 3166-1 alpha-2 values are required rather than relying on informal UK examples.

Safe use

• Always define a default destination.
• Avoid using country or device inference for access control.
• Test VPN, mobile, crawler, and unknown cases.
• Document which component supplies country data.
• Review privacy implications.

14. UTM and Campaign Management

UTM fields help identify campaign source, medium, campaign, term, and content values in analytics systems.

Campaign groups

Campaigns can be organized using hierarchical groups. A group can provide shared UTM defaults and aggregate activity.

Use a documented naming standard:

Avoid inconsistent capitalization and punctuation because analytics platforms can treat values as separate campaigns.

Campaign review

For each campaign:

• Confirm the destination.
• Confirm the redirect status.
• Confirm the date window.
• Confirm UTM values.
• Confirm whether tracking parameters are already present.
• Test the final URL.
• Review clicks and conversions.
• Review broken-link status.
• Retire or archive completed links.

15. Bulk Creation and Maintenance

The Bulk workspace can create or update managed links from:

• Pasted URLs
• WordPress posts
• Taxonomy terms
• WooCommerce products and product categories

Bulk actions can include approval, deletion, regeneration, and inline updates.

Safe bulk procedure

1. Export the current configuration.
2. Run a small staging batch.
3. Review generated slugs.
4. Review duplicate behavior.
5. Confirm destinations and redirect codes.
6. Confirm publication status.
7. Apply the production batch.
8. Review logs and recent links.
9. Roll back incorrect records before distributing URLs.

Bulk tools amplify both efficiency and mistakes. Do not generate thousands of public links without ownership, retention, and lifecycle rules.

16. Commerce Automation

The package detects WooCommerce and Easy Digital Downloads in the administration experience.

WooCommerce

Reviewed automation can create managed links for:

• Products
• Product categories

Activation can automatically enable commerce automation when WooCommerce is detected and schedule a recurring five-minute job. Generated records default to a review-oriented status in the reviewed configuration.

Important consent and workload caution

Automatic activation can create background work before an administrator deliberately opts in. Review automation settings immediately after activation on ecommerce sites.

Easy Digital Downloads

The interface can detect and mention Easy Digital Downloads, but the reviewed creation logic does not implement equivalent EDD product automation. Do not describe EDD automation as complete in version 1.2.

Recommended commerce workflow

• Disable automatic creation until approved.
• Define the slug template.
• Define UTM behavior.
• Decide draft versus published status.
• Test one product and category.
• Review product updates and deletions.
• Confirm that sale, account, cart, checkout, and private URLs are excluded.
• Monitor background-job duration.

17. Link Health

Aegisify Link can check destination status in scheduled batches and through manual actions.

Reviewed behavior includes:

• Daily scheduled checks
• Controlled batch sizes
• HEAD requests with a GET fallback
• Last-check timestamps
• Response-code evidence
• Broken or failed status
• Summary views

The reviewed workflow generally treats 2xx and 3xx responses as reachable.

Health-check interpretation

A successful response does not prove the content is correct. Review campaign-critical destinations manually.

Cron requirement

WP-Cron runs when WordPress receives traffic. Low-traffic sites can experience delayed checks and automation. Use a server scheduler when precise timing matters.

18. Analytics and Conversions

The package records click-level evidence and generates roll-up reports.

Reviewed analytics dimensions include:

• Total clicks
• Unique-click indicator
• Time series
• Top links
• Referrers
• Countries
• Devices
• Browsers
• UTM fields
• gclid and fbclid
• Bot or human heuristic
• Conversions
• Products and categories

Unique and human interpretations

A unique-click indicator is based on stored identifiers and does not prove a unique human. Bot classification is heuristic and can misclassify privacy tools, previews, monitoring systems, and unusual browsers.

Conversion markers

The package includes a conversion marker workflow through shortcode or AJAX behavior. Use it only for a clearly defined event such as:

• Completed signup
• Confirmed lead
• Completed purchase
• Approved download
• Scheduled appointment

Do not mark a page view as a conversion unless the business definition explicitly treats it that way.

Dashboard widget

A WordPress dashboard widget can show recent click activity. Limit dashboard access to roles that need campaign and visitor evidence.

19. Privacy and Data Handling

The reviewed click table can store or derive:

• Timestamp
• Link identifier
• Referrer
• Full user-agent string
• Salted SHA-256 IP hash
• Country
• Device
• Browser
• Conversion state
• UTM values
• Advertising click identifiers
• Persistent reference token

A reference cookie can persist for approximately 30 days.

Privacy requirements

• Update the site privacy notice.
• Define a lawful purpose for tracking.
• Minimize stored fields.
• Define retention.
• Restrict access.
• Avoid exporting personal data unnecessarily.
• Review advertising identifiers carefully.
• Test consent controls where required.
• Provide data-export and erasure handling appropriate to the site’s legal obligations.

Version 1.2 gap

Static review did not identify a complete built-in retention-pruning workflow or dedicated WordPress personal-data exporter and eraser integration for click records. Product owners should add those controls or document an approved operational process.

20. QR Codes

Managed links can expose a QR code generated through a configured provider. The reviewed default uses an external QR image service.

Before using QR codes:

• Confirm the external provider is approved.
• Review its privacy and availability terms.
• Avoid embedding sensitive destination data.
• Download and preserve campaign-critical QR assets.
• Test scanning after destination or slug changes.
• Do not claim the product has no external service dependency when the external QR provider is enabled.

21. CSV Import and Export

CSV tools can move managed-link records between environments or support bulk administration.

Export uses

• Change backup
• Agency review
• Migration
• Campaign approval
• Offline analysis

Import controls

1. Export the current state.
2. Use a trusted file.
3. Review headers and encoding.
4. Remove credentials or sensitive parameters.
5. Test a small batch.
6. Review duplicates and slug collisions.
7. Verify imported links.
8. Preserve an import report.

The reviewed parser is best suited to standard one-record-per-line CSV. Complex multiline quoted fields require additional validation.

22. AI Recommendations

The Recommendations workspace is optional and disabled by default.

When enabled, the reviewed workflow can send selected content context to a configured endpoint, including:

• Title
• Headings
• A limited content excerpt
• Internal and external link counts
• Existing anchors

The response can be stored as structured recommendations and issues for administrator review.

AI governance

• Confirm the endpoint owner.
• Review its data-processing terms.
• Use a scoped API credential.
• Do not send private or regulated content without approval.
• Keep recommendations human-reviewable.
• Do not automatically publish recommendations.
• Log approval and rejection decisions.
• Rotate credentials.
• Disable the service when not needed.

Version 1.2 advisory

The interface includes a Core service mode, but the reviewed request path relies on the configured endpoint URL. Confirm the production endpoint behavior before documenting a fully managed Aegisify AI service.

The recommendation table is initialized when the feature page is used. Visit and verify the workspace before relying on scheduled queue processing.

23. License and Optional Registration

The product can use Aegisify Core for Suite or Pro entitlement.

The optional free-install registration workflow requires explicit administrator opt-in and can transmit:

• Site domain
• Site URL
• WordPress administrator email
• WordPress version
• PHP version

Registration should remain optional and documented.

Version 1.2 interface advisory

The expected license-page file is absent from the reviewed package. This can prevent administrators from reaching the intended Tools & License interface. Use a corrected build before publishing setup instructions that depend on that page.

Packaging consistency

The reviewed Links Management implementation contains contradictory comments and enforcement behavior about whether Bulk and Manage are available in the Free edition. Commercial documentation should not publish a detailed matrix until rendering, server-side enforcement, pricing, and the License page use one entitlement map.

24. Operational Runbooks

Daily during rollout

• Review recent clicks.
• Review broken destinations.
• Confirm important shortlinks.
• Review unexpected automation.
• Confirm no Smart Link over-linking.
• Investigate conversion anomalies.

Weekly

• Run or review health checks.
• Review campaign groups.
• Review top links and referrers.
• Review bot-heavy activity.
• Review expired or near-expiration links.
• Review recent automated records.
• Confirm WP-Cron execution.

Monthly

• Export link configuration.
• Review privacy and retention.
• Review administrator access.
• Review inactive campaigns.
• Review external QR dependencies.
• Review AI endpoint and credentials.
• Test one conversion workflow.
• Review WooCommerce product and category automation.
• Confirm public guide and plugin versions.

Before a campaign launch

• Create the campaign group.
• Approve UTM naming.
• Create links in draft.
• Test redirects.
• Test device and optional country behavior.
• Test QR assets.
• Confirm expiration.
• Define conversion criteria.
• Define monitoring ownership.
• Publish only after acceptance.

After a domain or permalink change

• Save permalinks.
• Test /go/ or the configured prefix.
• Review destination URLs.
• Update canonical internal links.
• Re-run health checks.
• Purge caches.
• Test campaign links externally.
• Review imported or hard-coded QR assets.

25. Troubleshooting

Tools & License displays a missing-page notice

The reviewed package does not include the expected license-page file. Install a corrected package or obtain the missing supported file from Aegisify before relying on licensing and registration controls.

Smart Link does not appear

• Confirm the rule is active.
• Confirm the keyword is a supported one-word value.
• Confirm the content passes through an eligible filter.
• Check that the term is not inside an existing link or excluded element.
• Purge page and object caches.
• Test standard editor content separately from page-builder output.

Smart Link appears too many times

The reviewed implementation can link multiple occurrences. Narrow or disable the rule, use a more distinctive term, or wait for a build with occurrence controls.

Suggestions are blank

The version 1.2 suggestion source and interface expect different field names. Use a corrected build.

Managed link returns 404

• Save permalinks.
• Confirm the prefix.
• Confirm the slug and status.
• Check for route conflicts.
• Purge caches.
• Review security and redirect plugins.
• Test the direct destination.

Country targeting does not work

Confirm that another trusted component provides country data through the required filter. Aegisify Link 1.2 does not include a full GeoIP provider.

Health checks run late

Confirm WP-Cron and use server cron when precise timing matters.

Click count is unexpectedly high

Review user agents, referrers, social previews, bot classification, monitoring systems, and repeated test traffic.

WooCommerce links appear without deliberate setup

Review automation settings immediately after activation. The package can auto-enable commerce automation when WooCommerce is detected.

EDD links are not generated

Version 1.2 can detect Easy Digital Downloads in the interface, but equivalent automated record creation is not implemented in the reviewed logic.

Word Cloud footer cannot be disabled

The reviewed settings save path forces the footer option back on. Use a corrected build before publishing a no-branding option.

AI recommendations do not run

• Confirm opt-in.
• Confirm endpoint URL.
• Confirm API key.
• Confirm outbound HTTPS.
• Visit the Recommendations page to initialize the table.
• Check WP-Cron.
• Review logs and endpoint responses.
• Confirm the endpoint accepts the expected request and response format.

26. Frequently Asked Questions

Does Aegisify Link guarantee higher rankings?

No. It helps create and manage links. Search outcomes depend on relevance, content quality, crawlability, architecture, competition, and search-engine systems.

Can Smart Links match phrases?

The reviewed 1.2 implementation is designed around one-word keyword rules. Do not promise arbitrary phrase replacement without a validated newer build.

Does every click represent a person?

No. Bots, previews, monitoring, and repeated visits can create click records.

Can I use 301 for every managed link?

No. Use 301 only when the redirect is intended to be permanent. Use a temporary code during testing or time-limited campaigns.

Does the health checker find every broken-link problem?

No. It detects HTTP and transport behavior. It does not prove that the destination content is correct or commercially valid.

Is country targeting built in?

The routing extension exists, but country data must be supplied by another trusted component.

Is the QR code generated locally?

The reviewed default uses an external QR image provider.

Does Aegisify Link support WooCommerce?

Yes, the reviewed automation includes WooCommerce product and product-category workflows. Test the deployed configuration before broad automation.

Does it automate Easy Digital Downloads links?

The interface detects EDD, but the reviewed version does not implement equivalent EDD link creation.

Does AI automatically change content?

The reviewed recommendations workflow stores recommendations for review. Keep a human approval step and do not promise autonomous changes.

27. Glossary

28. Related Resources

• Aegisify Link product page
• Aegisify Link User Guide
• Aegisify Help Center
• Aegisify Link health and campaign article
• Google link best practices
• Google redirects guidance
• WordPress Cron documentation
• WordPress Privacy Handbook
• WordPress personal-data exporters
• WordPress personal-data erasers

29. Final Operational Recommendation

Begin with one managed link, one narrow Smart Link, one health check, and one analytics test. Establish campaign naming, privacy, retention, redirect, and ownership standards before enabling bulk or automated creation. Correct the missing License page, suggestion schema, entitlement behavior, Word Cloud footer control, EDD messaging, and automation-consent issues before presenting version 1.2 as fully production-complete.