INTERNAL LINK ANALYSIS & PLANNING

It shows supported content as nodes and detected internal links as connections, helping you understand the structure around each page.

The graph and page inspection views can reveal content with few or no detected inbound connections within the configured scope.

It does not turn every recommendation into an uncontrolled edit. Supported changes use the available review, preview and apply workflow.

Yes. Select or search for a page to focus on its inbound links, outbound links and nearby content.

Yes. Supported filters and boundaries help reduce the visible graph by status, content type, cluster or taxonomy.

Yes. Supported WordPress content types can be included according to the plugin configuration.

Supported product content can be included when WooCommerce and the relevant content scope are configured.

The interface provides bounded neighbourhood views, with supported depth controls designed to keep exploration understandable.

Detection follows the plugin’s canonical internal-link rules and configured scope, rather than treating every raw URL as equally meaningful.

Yes. Page inspection includes useful relationship counts and network context for supported nodes.

Yes. Internal Link Network can build and present its own link graph. Apollo adds complementary planning and cluster context when connected.

Internal Link Network remains the owner of link-edge data, while Apollo can consume supported summaries for planning.

It helps you compare the intended cluster with the actual published links, so your team can strengthen useful relationships.

Recommendations depend on the supported workflow. Editors should always confirm that anchor wording is natural, accurate and useful.

No. Relevance and reader value matter more than volume. The graph helps you make selective, informed improvements.

Yes. Rebuilding refreshes the network so the view reflects meaningful changes to supported content and links.

Viewing and rebuilding the graph do not rewrite content. A live change only occurs through an explicit supported apply action.

Its primary job is the internal content network. Do not buy it as a general external broken-link crawler.

That advanced workflow requires the compatible Apollo, Workflow Genie, MCP and AI Team components in addition to Internal Link Network.

No. It helps improve internal structure and decision quality, but search results depend on many additional factors.

A2A Internal Link Network scans supported WordPress content and turns internal links into an interactive graph. You can explore pages, relationships and recommendations before making controlled improvements.

It is best for sites with enough content that internal linking can no longer be checked reliably from memory or a simple list.

It is not designed for buyers who want mass automatic link insertion without reviewing reader value and context.

Yes. A2A Internal Link Network is a WordPress product, so your site remains the working environment rather than a separate publishing platform.

A compatible self-hosted WordPress site with supported content available for scanning.

No. Core link detection, graph building and inspection are deterministic. AI is only relevant to optional connected workflows.

The graph is built from supported content and link relationships in your WordPress site. Optional connected workflows follow their own explicit configuration.

Yes. You can cancel before the next renewal. Check the current checkout terms for billing and any refund eligibility.

An active subscription provides the licensed product entitlement and the updates or support described in the current purchase offer.

Yes. The current monthly option is £4.99 per month.

Yes. The current annual option is £49.99 per year.

The primary purchase button uses product mapping 16. The second option uses mapping 9.

Site coverage depends on the licence or offer selected at checkout. Confirm the current allowance before buying for multiple sites.

Yes. The sales and product experience is designed to turn technical work into clearer decisions. Initial configuration may still benefit from an experienced WordPress administrator.

No. It reduces repetitive work and improves context, but an authorised person should still confirm accuracy, relevance and business fit.

Important changes follow the controls provided by the product. Review settings, user permissions and any preview or apply step before enabling wider use.

Use WordPress roles, capabilities and any product-specific access settings to limit administrative and workflow actions.

The product is designed for WordPress, but performance always depends on site size, hosting, configuration and the operation being run. Test substantial scans or batch work on a suitable environment.

Supported custom post types can be included where the product exposes a content-scope setting and the type supplies the information the feature needs.

WooCommerce compatibility depends on the feature. Supported product content can participate where the product documentation and configuration allow it.

The product should keep the failure visible and provide useful state or diagnostic information rather than treating incomplete work as successful.

Yes. Testing configuration and higher-impact workflows on staging is sensible, especially for large sites or batch operations.

A focused setup can begin quickly, but complete configuration depends on site size, data quality, integrations and the team workflow you want to establish.

No. It improves the process, evidence and execution available to your team. Rankings, engagement and sales also depend on the market, offer, content and many external factors.

Confirm that your site meets the requirements, that the selected licence covers the required sites and that A2A Internal Link Network solves the workflow problem described on this page.