CircleCI

SEO validation in your CircleCI pipeline.

Add Indxel to your CircleCI config to validate SEO on every commit. Run checks after your build job and block deployments when critical SEO issues are found.

1.Add to .circleci/config.yml

yaml

version: 2.1

jobs:
  build:
    docker:
      - image: cimg/node:20.0
    steps:
      - checkout
      - restore_cache:
          keys:
            - deps-{{ checksum "package-lock.json" }}
      - run: npm ci
      - save_cache:
          paths:
            - node_modules
          key: deps-{{ checksum "package-lock.json" }}
      - run: npm run build
      - persist_to_workspace:
          root: .
          paths:
            - .next
            - node_modules

  seo-check:
    docker:
      - image: cimg/node:20.0
    steps:
      - checkout
      - attach_workspace:
          at: .
      - run: npx indxel check --ci

workflows:
  build-and-check:
    jobs:
      - build
      - seo-check:
          requires:
            - build

Why use Indxel with CircleCI

✓Add SEO validation as a dedicated job in your CircleCI workflow with full parallelization
✓Use workspace artifacts to share build output between build and SEO check jobs
✓Cache node_modules for faster subsequent SEO checks across pipeline runs
✓Block deployments when critical metadata issues are detected in the SEO check job

Frequently asked questions

Can the SEO check run in parallel with tests?

Yes. Configure your CircleCI workflow to run the seo-check job in parallel with test jobs, both depending on the build job. This does not add time to your pipeline.

How do I persist results between jobs?

Use CircleCI workspaces to pass the build output (.next directory) from the build job to the seo-check job. The check uses the built artifacts for static analysis.