How publication moderation works

Moderation means checking content against the rules of DevKG. It helps keep out spam, deception and unsuitable publications. This guide covers vacancies, events and articles submitted for publication.

What happens after submission

A company representative may need to approve the content first. If the order includes paid services, complete payment next. Payment does not itself mean approval. Publishing articles is free.

The next step depends on the site’s settings:

Review routeWhat happens
Automatic check firstContent may publish immediately or go to a person for review
Human review firstContent waits for a moderator’s decision

In the current publication flow, automatic checks do not reject vacancies, events or articles: content that does not pass is sent to a person. This does not describe every section; comments, for example, have a separate review process.

A company’s verification badge does not guarantee immediate publication or exemption from the rules. Some content from verified companies may also be checked after publication.

1. Check the status

Open your content list from your profile. Only sections enabled on the site are available:

StatusWhat to do
Awaiting company approvalWait for a colleague who can approve publications
Awaiting paymentComplete payment; if already charged, check the transaction first
Under reviewWait for the team’s decision
PublishedOpen the content and check how it looks
RejectedOpen the rejection screen and request reconsideration if needed

For payment problems, use the payment troubleshooting guide.

2. Wait for a decision

The posting rules give a usual timeframe of up to one business day, or up to two business days during busy periods. This is the policy’s usual timeframe, not an on-screen countdown. Check the applicable edition of the document.

Check your list and notifications. If the wait is longer, contact support with the content link and submission date. Do not create identical copies to speed up review.

3. If the content is rejected

Select Rejected. The screen reports rejection or removal but does not show the exact rule triggered. Use its contact button to ask for an explanation and review by a person.

Editing or pressing Publish again does not itself remove the rejection. If you corrected the content, list the changes in your request. See What to do after rejection.

Returning content to review does not guarantee approval. For paid content, the terms provide for review again without a new payment; refunds depend on delivered services and applicable terms. See Refunds. Having points does not determine eligibility.

Editing published content

Content changes may trigger another review. The fields that trigger it depend on the publication type. Check the status after saving; do not assume every typo correction is exempt.

Before submitting

  • Describe a real job, event or experience relevant to the site’s audience.
  • Use a clear title without unrealistic income promises or “URGENT!!!”.
  • Give accurate terms, dates, prices and contact details; use dedicated fields as intended.
  • Do not charge job seekers to apply or get hired. A paid event ticket is different: state its price honestly.
  • Do not publish other people’s text or personal information without the right to do so.

This is a checklist, not the full rules. Consult the posting rules of your site.

Reporting someone else’s content

Use Report when available and describe the issue. Otherwise contact support with a link. Review deadlines depend on the complaint type and are set out in the rules; not every complaint is handled within one day.

A report does not automatically establish that the author broke a rule. The team checks before deciding.

Was this article helpful?

Can't find an answer? Contact support