> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Strapi on Vortex IQ

> Monitor Strapi publishing, engagement and freshness, and catch decay before organic reach erodes.

Monitor Strapi publishing, engagement and freshness, and catch decay before organic reach erodes.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=strapi)

<CardGroup cols={5}>
  <Card title="18">
    performance signals
  </Card>

  <Card title="2">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Customer experience (10 signals)">
        | Signal                          | Alert behaviour        | What it tracks                                                                                                |
        | ------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------- |
        | **Accessibility Score**         | Alert band 90 / 70     | Lighthouse accessibility category (0-100).                                                                    |
        | **CLS (Mobile)**                | Alert band 0.1 / 0.25  | Cumulative Layout Shift p75 (mobile). Good \<0.1, poor >0.25.                                                 |
        | **CWV Pass Rate (Mobile)**      | Alert band 75 / 50     | Share of real-user sessions passing all three Core Web Vitals (mobile). Good >75%.                            |
        | **INP (Mobile)**                | Alert band 200 / 500   | Interaction to Next Paint p75 (mobile). Good \<200ms, poor >500ms.                                            |
        | **LCP (Mobile)**                | Alert band 2500 / 4000 | Largest Contentful Paint p75 from the Strapi site's CrUX field data (mobile). Good \<2.5s, poor >4s.          |
        | **Performance Score (Desktop)** | Alert band 90 / 50     | Lighthouse performance category (0-100), desktop strategy.                                                    |
        | **Performance Score (Mobile)**  | Alert band 90 / 50     | Lighthouse performance category (0-100), mobile strategy. Good >=90, poor \<50.                               |
        | **Render-Blocking Resources**   | Alert band 200 / 500   | Lighthouse render-blocking-resources audit - wasted ms from blocking CSS/JS the Strapi theme ships.           |
        | **Speed Index**                 | Alert band 3400 / 5800 | Lighthouse speed-index audit (ms) - how quickly content is visually populated.                                |
        | **TTFB (Mobile)**               | Alert band 800 / 1800  | Time To First Byte p75 (mobile) - the headless API-call cascade shows up here first. Good \<0.8s, poor >1.8s. |
      </Accordion>

      <Accordion title="Catalogue quality (4 signals)">
        | Signal                   | Alert behaviour              | What it tracks                                                                        |
        | ------------------------ | ---------------------------- | ------------------------------------------------------------------------------------- |
        | **Best Practices Score** | Alert band 90 / 70           | Lighthouse best-practices category (0-100).                                           |
        | **Stale Content**        | Alert band 10 / 40           | % of entries (sampled, up to 100) not updated in the last 12 months.                  |
        | **Total Blocking Time**  | Alert band 200 / 600         | Lighthouse total-blocking-time audit (ms) - main-thread blocking between FCP and TTI. |
        | **Total Page Weight**    | Alert band 1572864 / 3145728 | Lighthouse total-byte-weight audit (bytes transferred). Good \<1.5MB, poor >3MB.      |
      </Accordion>

      <Accordion title="Grow revenue (3 signals)">
        | Signal                      | Alert behaviour    | What it tracks                                                                             |
        | --------------------------- | ------------------ | ------------------------------------------------------------------------------------------ |
        | **Publishing Cadence**      | Alert band 4 / 1   | Entries published under the configured content type in the last 30 days.                   |
        | **SEO Score**               | Alert band 90 / 70 | Lighthouse SEO category (0-100). Crawlability/markup hygiene of the Strapi-rendered pages. |
        | **Slow High-Traffic Pages** | Merchant rule      | Slow High-Traffic Pages, broken down by row.                                               |
      </Accordion>

      <Accordion title="Protect revenue (1 signals)">
        | Signal                        | Alert behaviour | What it tracks                                            |
        | ----------------------------- | --------------- | --------------------------------------------------------- |
        | **Bounce Lift on Slow Pages** | Watch only      | Description pending editorial review; the signal is live. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (2)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="Over 40% of content not updated in 12 months">
        **Severity** medium · **Outcome** Catalogue quality · **Fix status** Report only

        When over 40 percent of content has not been touched in a year, decay outpaces creation; rankings quietly rot page by page.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `CMS-STALE-001`
      </Accordion>

      <Accordion title="Publishing pipeline stalled (no post in 30 days)">
        **Severity** medium · **Outcome** Run operations · **Fix status** Candidate remediation

        A stalled publishing pipeline slowly starves organic traffic; content compounds only while it keeps shipping.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `CMS-PUBLISH-001`
      </Accordion>
    </AccordionGroup>

    #### Build your own automated fixes

    Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change.
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **4 read** and **1 write** operations across contenttypes, contenttypebuildercontenttypes, runpagespeeds, usermes on Strapi. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=strapi)

    #### Ready to build your first Strapi workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource                       | Read operations | Write operations |
      | ------------------------------ | --------------- | ---------------- |
      | contenttypes                   | 1               | 1                |
      | contenttypebuildercontenttypes | 1               | 0                |
      | runpagespeeds                  | 1               | 0                |
      | usermes                        | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>
