Editorial Policy

Editorial Policy

This Editorial Policy explains how Rebab.org plans, writes, reviews, updates, and corrects content. Our goal is to publish clear, careful, and useful information about the rebab, rabab, rubab, and related traditional string instruments.

Rebab.org covers a subject where names, spellings, construction styles, playing methods, and cultural meanings can change across regions. Because of that, our editorial work must be patient. We avoid treating every similar word as the same instrument, and we try to explain regional differences in a way that is readable for beginners without flattening the history behind the music.

Our Editorial Mission

Rebab.org exists to make information about the rebab family of instruments easier to understand and easier to verify. We publish educational content for readers who want a reliable starting point, whether they are music students, teachers, collectors, performers, museum visitors, researchers, or curious readers.

The site focuses on the rebab, rabab, rubab, rubāb, rababa, rebap, rubob, and related traditional string instruments. We also cover connected topics such as early bowed instruments, regional instrument families, construction methods, tuning notes, cultural heritage, and instrument comparisons.

Our editorial mission is not to make the subject sound more certain than it is. Some instrument names have overlapping histories. Some sources use different spellings. Some regional forms are closely related, while others only appear similar in English transliteration. A useful article should help the reader understand that complexity without making the page feel heavy.

Topics We Cover

Rebab.org is built around a focused topic area. We do not publish unrelated general music content just to increase traffic. Articles should connect naturally to the rebab, rabab, rubab, or the wider family of traditional string instruments that help explain them.

Main editorial topic areas covered by Rebab.org.

Topic Area	What It Includes	Editorial Purpose
Rebab Basics	Meaning, pronunciation, spelling, instrument type, common questions, and beginner explanations.	Help new readers understand the subject quickly and accurately.
Regional Forms	Afghan rubab, Arabic rabab, Indonesian rebab, Turkish rebab or rebap, Persian rubab, Central Asian rubab, and other local forms.	Show how instrument names and structures change across cultures and regions.
History	Early bowed instruments, medieval references, rebec connections, migration of instrument forms, and historical classification.	Give readers deeper context without turning every article into a long academic essay.
Construction and Materials	Body shapes, soundboards, skin heads, strings, bows, bridges, resonators, woods, decoration, and craftsmanship.	Explain what the instrument is physically and how different forms are built.
Sound and Playing	Bowed and plucked forms, tuning notes, playing position, ensemble use, tone, and performance setting.	Help readers connect the instrument’s structure to the way it is played and heard.
Comparisons	Rebab vs rabab, rabab vs rubab, rubab vs sarod, rebab vs rebec, rebab vs kamancheh, and related comparisons.	Resolve common confusion and support searchers who are comparing similar names or instruments.
Cultural Context	Cultural heritage, craft traditions, regional identity, museum collections, music lineages, and educational references.	Treat instruments as living cultural objects, not just technical items.

What We Do Not Cover

Rebab.org is not a general entertainment website, a marketplace, a repair shop, or a music school. We may discuss learning, buying, tuning, construction, and repair in general educational terms, but we do not provide personal instruction, instrument authentication, appraisal, restoration services, or seller guarantees.

We also avoid unrelated celebrity news, gossip, political commentary, broad culture-war topics, and thin content created only around high-volume keywords. The site should stay focused. A small, trustworthy reference library is more valuable than a large website filled with weak pages.

How We Choose Article Topics

Article topics are selected based on reader usefulness, search intent, topical relevance, and the ability to answer a question with dependable information. A topic should help the site become clearer and more complete, not just larger.

Before creating a new article, we consider whether the page should exist as a standalone guide, a section inside a broader article, a comparison page, a glossary entry, or a supporting internal link. This prevents unnecessary overlap and keeps the site structure easier to use.

• Reader need: Does the topic answer a real question a reader may have?
• Search intent: Is the reader looking for a definition, comparison, history, practical explanation, or source-based reference?
• Topical fit: Does the topic connect naturally to rebab, rabab, rubab, or related traditional string instruments?
• Source availability: Can the article be supported with reliable references or careful source-aware wording?
• Internal link value: Will the page strengthen the surrounding topic cluster and help readers move through the site?
• Long-term usefulness: Is the topic likely to remain useful beyond a short trend?

Search Intent and Page Format

Different searchers need different page formats. Someone searching “what is a rebab” needs a direct explanation first. Someone searching “rebab vs rubab” needs a comparison. Someone searching “Afghan rubab tuning” may need a practical guide with careful regional notes. We match the page format to the reader’s likely intent.

How Rebab.org matches search intent with editorial page formats.

Search Intent	Example Query	Preferred Page Format
Definition	What is a rebab?	Direct answer, basic explanation, history note, regional distinctions, and FAQ.
Comparison	Rebab vs rabab vs rubab	Comparison table, spelling notes, regional use, and clear difference summary.
Regional Research	Afghan rubab	Instrument profile with origin, structure, sound, cultural context, and related instruments.
Historical Research	Rebab instrument history	Timeline-style explanation, source notes, historical caution, and related instrument links.
Practical Learning	How many strings does a rubab have?	Careful answer with instrument-type distinctions and warnings about regional variation.
Cultural Context	Rubab cultural heritage	Contextual article with heritage references, craft tradition, and regional identity notes.

Research Standards

Research for Rebab.org should be careful and proportionate. A basic page does not need to read like a thesis, but it still needs to be accurate. A deeper historical or cultural article should rely on stronger references and clearer distinctions.

We prefer sources that help readers verify the information. When possible, articles should draw from museum records, cultural heritage organizations, academic publications, university materials, music dictionaries, archive records, instrument collections, books, and carefully documented educational resources.

We are cautious with unsourced blog posts, copied product descriptions, AI-generated pages, vague encyclopedic summaries, forum comments, and pages that repeat short claims without showing where the information came from. These may be useful for finding leads, but they should not be the foundation of an article.

Preferred Source Types

• Museum collections: object records, catalog notes, material descriptions, collection histories, and curatorial essays.
• Cultural heritage organizations: pages that document living traditions, craftsmanship, performance practices, and regional context.
• Academic sources: books, journal articles, university pages, theses, musicology materials, and ethnomusicology references.
• Specialized music references: instrument dictionaries, historical music resources, archive entries, and documented field recordings.
• Institutional sources: libraries, universities, archives, conservatories, and public cultural institutions.
• Primary or near-primary sources: maker documentation, performer explanations, interviews, and teaching materials when they are clearly attributable.

Sources We Treat Carefully

• Pages with no author, institution, date, source list, or clear editorial responsibility.
• Generic instrument descriptions copied across multiple websites.
• Sales pages that describe an instrument mainly to promote a product.
• Short social posts that make broad historical claims without evidence.
• Forum comments that may be useful as personal experience but not as verified reference material.
• Automatically generated pages that combine facts without cultural or historical context.

Handling Spelling Variations

Spelling variations are central to this site. Rebab, rabab, rubab, rubāb, rebap, rababa, and rubob may appear in different languages, regions, and cataloging traditions. We do not assume that one spelling is always correct and the others are wrong.

When writing about a spelling, we try to explain where it appears, how it is commonly used, and whether it points to a specific regional instrument or a broader family of related instruments. If sources use different spellings, we may mention that difference directly.

Cultural Respect and Regional Context

The instruments covered on Rebab.org are connected to living traditions. They may appear in classical music, folk music, court music, devotional settings, family traditions, teaching lineages, craft practices, and regional identity. We try to write with that context in mind.

An article should not reduce a traditional instrument to a few technical details. Construction, strings, tuning, and sound matter, but so do the people who play the instrument, the places where it is heard, and the traditions that keep it alive.

When a topic involves a specific culture, region, language, or community, we try to avoid careless generalization. If a claim applies only to one regional form, the article should not present it as true for every rebab, rabab, or rubab.

Accuracy and Fact-Checking

Before publication, content should be checked for basic factual accuracy, spelling consistency, source support, internal logic, and reader clarity. The level of review depends on the complexity of the topic, but every page should be written with care.

Fact-checking is especially important for historical claims, origin claims, regional classifications, instrument construction, tuning, string count, cultural heritage status, and comparisons between related instruments. These are areas where online sources often simplify too much.

• We avoid presenting uncertain claims as settled facts.
• We identify regional variation when it changes the answer.
• We avoid copying a source’s wording unless a short quotation is clearly useful and properly attributed.
• We check whether similar names refer to the same instrument, related instruments, or different regional forms.
• We update pages when stronger information becomes available.
• We correct errors when a correction improves accuracy, clarity, or cultural context.

How We Write Definitions

Definition pages should begin with a direct answer. Readers should not have to scroll through a long introduction before learning what the instrument is. After the direct answer, the article can explain history, names, regional differences, sound, construction, and related instruments.

A good definition on Rebab.org should answer the main question quickly, then add enough context to prevent misunderstanding. For example, a page about the rebab should explain that the word can refer to different bowed or plucked instruments depending on region and spelling.

How We Write Comparison Pages

Comparison pages are important because many readers arrive with confusion. They may want to know whether rebab and rabab are the same, whether rubab is a different instrument, or whether a regional instrument is related to another string instrument.

Each comparison page should include a clear short answer, a comparison table, separate explanations for each instrument or term, and a section explaining when the names overlap. If the answer depends on region, the page should say so plainly.

Internal Linking Standards

Internal links help readers understand a topic step by step. They also help organize the site into clear topic clusters. Links should be useful and natural, not forced into every paragraph.

When an article mentions a related instrument, regional form, spelling variation, or broader category, it may link to a stronger supporting page. For example, a page about the Afghan rubab may link to rubab vs sarod, rubab construction, Central Asian rubab, and rebab vs rabab vs rubab if those pages help the reader.

• Use descriptive anchor text rather than vague phrases such as “click here.”
• Link to the most relevant page, not just the newest page.
• Avoid adding too many internal links in one short section.
• Use comparison pages to connect similar instruments and spelling variations.
• Use glossary pages to support terms that appear across many articles.
• Update older pages when better supporting content is published.

External Link Standards

External links should support verification, further reading, or reader understanding. We prefer linking to reliable sources rather than low-quality summaries. A link should earn its place on the page.

When possible, external references should point to the most stable and useful source available. For example, a museum object record is often better than a copied image page, and a cultural heritage organization page is often better than a short unsourced article that repeats the same claim.

External links may change or disappear over time. If we find broken links, outdated pages, or sources that no longer support the statement being made, we may update or remove those references.

Use of Tables, Lists, and Gutenberg Blocks

Rebab.org uses readable page elements to make detailed information easier to scan. Tables are useful for comparisons, regional differences, strings, materials, and source-based distinctions. Lists are useful when several small points need to be understood quickly.

Design elements should support understanding. They should not be added only for decoration. A table should make comparison easier. A highlight box should draw attention to a real caution or important distinction. A button should guide readers to a useful next page.

• Tables should include clear column labels.
• Comparison tables should avoid vague wording where the topic needs precision.
• Lists should be used for scanability, not as a replacement for explanation.
• Callout boxes should highlight important editorial cautions or reader guidance.
• Buttons should point to relevant internal pages, not unrelated content.

Use of Images, Audio, and Media

Traditional instruments are visual and sonic subjects, so media can help readers. Images may show instrument structure, materials, shape, decorative work, or regional differences. Audio and video may help readers understand sound and playing style.

When using media, we aim to respect copyright, cultural context, and source attribution. We should not use images, recordings, or videos in a way that suggests ownership or endorsement when none exists. Public-domain, museum-provided, properly licensed, or embedded third-party media should be handled according to the terms of the source.

Media should not replace written explanation. A page should still explain what the reader is seeing or hearing, why it matters, and whether the example represents one regional form rather than the entire instrument family.

AI-Assisted and Tool-Assisted Content

Rebab.org may use digital tools to help with drafting, editing, outlining, formatting, research organization, grammar checking, or content planning. These tools can support the editorial process, but they do not replace human review.

Any tool-assisted content should be checked for accuracy, clarity, source support, and cultural context before publication. This is especially important for instrument names, historical claims, regional details, and technical descriptions, where automated tools may blend similar facts or miss important distinctions.

We do not aim to publish unreviewed, mass-produced, or thin automated content. The purpose of Rebab.org is to build a focused educational resource, not to fill the site with pages that repeat the same general information.

Advertising, Affiliate Content, and Editorial Independence

Rebab.org may display advertising or use affiliate links in the future. These features may help support the operation of the website, but they should not control the editorial direction of the site.

Editorial content should be written to help readers first. If a page includes buying guidance, book suggestions, instrument resources, or product-related links, the information should remain balanced and practical. A commission opportunity is not a reason to recommend something unsuitable or to hide important limitations.

• Advertising should not decide the factual position of an article.
• Affiliate links should not be disguised as neutral source citations.
• Sponsored material, if ever accepted, should be clearly identified.
• Educational references should not be replaced with commercial links when a stronger source is available.
• Buying-related pages should avoid guarantees about authenticity, value, quality, or suitability.

Corrections Policy Overview

We welcome correction requests. Readers may notice an unclear sentence, outdated source, spelling issue, missing regional distinction, or factual mistake. Because this site covers culturally specific instruments, corrections can be valuable.

Correction requests should include the page URL, the sentence or section involved, a short explanation of the issue, and a reliable source if available. We review requests carefully and update pages when a correction improves accuracy, clarity, or usefulness.

Not every suggested change will be accepted. Some suggestions may reflect a different regional usage, a personal preference, or a source that does not support the proposed edit. When needed, we may revise a sentence to show multiple accepted views instead of replacing one narrow claim with another.

Review and Update Process

Content may be reviewed when new sources are found, when a reader sends a correction, when an article becomes outdated, when internal links need improvement, or when a topic cluster grows enough to require restructuring.

Some pages need more frequent review than others. A basic definition may remain stable for a long time. A page about cultural heritage status, museum references, media embeds, or external resources may need updates when sources change.

General review approach for different types of Rebab.org content.

Content Type	Review Trigger	What We Check
Definition Pages	Reader confusion, source improvements, or better internal links.	Clarity, spelling distinctions, basic accuracy, and FAQ usefulness.
Regional Instrument Pages	New source, correction request, or missing cultural context.	Regional accuracy, naming, construction, sound, and cultural notes.
Comparison Pages	New related article, search intent shift, or unclear distinction.	Comparison table, overlap notes, internal links, and direct answer quality.
Historical Pages	Better academic or museum source becomes available.	Timeline accuracy, origin claims, source quality, and cautious wording.
Buying or Resource Pages	Link changes, seller changes, product changes, or affiliate updates.	Availability, disclosure, link accuracy, and reader safety.
Policy Pages	Site feature changes, legal changes, contact changes, or service changes.	Accuracy, transparency, contact details, and internal policy consistency.

Handling Uncertainty

Some questions do not have one clean answer. A source may use one spelling. A performer may use another. A museum catalog may classify an object differently from a regional musician. In those cases, we try to write with honest uncertainty.

Useful uncertainty is not weakness. It helps readers understand the topic more accurately. Instead of forcing a single answer, an article may say that a term is used differently across regions, or that a historical link is often suggested but not always described in the same way by all sources.

Originality and Plagiarism

Rebab.org articles should be written in original language. Research can be based on external sources, but the final article should not copy source wording, structure, or descriptions in a way that misleads readers or violates copyright.

Short quotations may be used when they are useful, limited, and properly attributed. Most of the time, paraphrasing with clear source awareness is better for readability. We aim to explain, not to copy.

Reader Safety and Practical Advice

Some pages may discuss buying, tuning, repairing, restoring, or identifying instruments. These topics can affect money, instrument condition, and cultural value, so we treat them carefully.

Rebab.org does not authenticate instruments, appraise value, guarantee seller quality, or provide personal repair instructions for a specific item. Practical pages should remind readers to consult experienced teachers, makers, restorers, appraisers, or regional specialists when a decision has real financial or technical importance.

Tone and Readability

The site should sound calm, informed, and human. Articles should be clear enough for beginners but not so simplified that they erase important differences. We prefer plain English, varied sentence lengths, short sections, and direct explanations.

We avoid empty introductions, exaggerated claims, filler paragraphs, and repeated phrases that make content feel mechanical. A page should answer the reader’s question early, then add depth through useful structure.

• Use direct answers near the beginning of informational pages.
• Break complex ideas into smaller sections.
• Use tables when comparison helps the reader.
• Avoid dramatic or promotional wording.
• Explain technical terms when they matter.
• Do not overuse the same keyword in unnatural ways.
• Write for people first, while keeping search intent and structure in mind.

SEO and Editorial Quality

Rebab.org uses SEO to make useful pages easier to find. SEO should support editorial quality, not weaken it. We do not publish pages only because a keyword exists. A page must serve a reader and fit the site’s topic map.

Our SEO approach is based on topical authority, search intent, semantic coverage, internal linking, clean headings, useful tables, and strong page structure. Articles should cover related entities naturally. For example, a page about the rubab may mention Afghanistan, Central Asia, sarod, strings, resonator, plectrum, and cultural heritage when those details genuinely help the article.

Keyword use should feel natural. We would rather publish one careful guide that answers the question well than repeat the same phrase many times across a thin page.

Policy for Sponsored or Guest Content

Rebab.org does not accept content that is designed mainly to manipulate search rankings, hide advertising, or place paid links without clear disclosure. If guest contributions or sponsored content are ever accepted, they must meet the same editorial standards as other pages and must be clearly identified where required.

We may reject submissions that are promotional, inaccurate, copied, irrelevant, poorly sourced, culturally careless, or not useful for readers. Payment or partnership does not guarantee publication.

Contacting Us About Editorial Matters

Readers may contact Rebab.org about corrections, source suggestions, editorial questions, unclear wording, missing regional context, or topic ideas. Clear messages are easier to review.

When contacting us about an article, please include the page URL, the sentence or topic involved, and any reliable source that supports your suggestion. If the issue is about a regional name or cultural context, include the relevant country, language, musical tradition, or instrument type if you know it.

Changes to This Editorial Policy

This Editorial Policy may be updated as Rebab.org grows. Updates may reflect changes in source standards, content formats, review processes, advertising disclosures, guest content rules, internal linking structure, or correction procedures.

When this page is updated, the “Last Updated” date near the top of the page will be changed. The current version of this page explains the editorial standards we aim to follow across Rebab.org.