← All projectsProject / SEO & editorial operations

SEO, editorial work and link monitoring

A workspace for editorial production, link placements and checks of published pages.

FastAPICeleryPostgreSQLRedisPlaywrightAngular
Project overview

What the service does

A work-management tool for SEO and content teams. It tracks article preparation and placement orders, then checks whether each published page still has the expected link, anchor and page directives.

Content production, placement orders and link checks need to stay connected so a team can see what was published and whether the link is still there.

Who uses it

SEO specialists, link-placement teams, editors and team leads coordinating content and placements.

Input
  • A content task, author/editor assignment and approval state.
  • An ordered placement URL and the link expected on the page.
  • Scheduled checks of published pages.
Output
  • A shared view of content and placement status.
  • History of page, link, anchor and rel/robots checks.
  • Placement status showing whether the expected link was found, changed or removed.
01 / How the service works

Editorial work and placements

Editorial work and placements

  1. INPUTContent task

    Assign an editor and track approval

  2. PROCESSLink placement order

    Connect publication and payment workflow

  3. CHECKCheck the published page

    Find the target URL, anchor and link status

  4. RESULTSave the result

    Keep status and repeat checks over time

02 / System architecture

Main components and their roles

Roles / assignments

Plan content

Create an editorial task and assign responsibility.

How it works

Role-dependent transitions preserve assignments, approvals and history.

Orders / integration

Track placement

Connect the publication workflow to placement and payment requests.

How it works

External order synchronization has its own state and permitted transitions.

HTTP / proxy / browser

Verify the page

Inspect the page and the expected link.

How it works

HTTP checks can fall back to proxy and WebKit; anchor, rel and robots metadata are inspected.

Celery / check history

Check again

Scheduled jobs preserve observations over time.

How it works

History and latest status are stored separately. Redis overlap protection fails open on infrastructure error.

03 / Implementation details

Engineering decisions

01

Plan editorial work

Create content tasks, assign editors and track approvals and placement orders.

02

Check published links

Inspect the destination page, anchor text and rel/robots directives.

03

Schedule repeat checks

Background jobs revisit published pages and save each result.

Software development for business

Have a project in mind?

Tell me what the application should do, how the team works today and which requirements or deadlines matter.