Planner ✅ ❌ 卐💥

Planner - White Board

User Flow - JobSalary.IN

Listings 1

1
Office Attendant Salary in India (2026)

(1) Company-wise Office Attendant Salaries
SBI - 25000
RBI - 23000
NABARD - 34000

(2) Latest 5 Office Attendant Recruitment Notifications (TABLE)
RBI Office Attendant Recruitment 2026
NABARD Office Attendant Recruitment 2026

tag - main-salary, office-sttendant(salary/jobs)
2
3
#
4
#
5
#
6
#

Listings 2 OR Templates

1
Office Attendant Jobs in India (2026)

All Latest Office Attendant Recruitment Notifications (TABLE)
RBI Office Attendant Recruitment 2026
NABARD Office Attendant Recruitment 2026
... 
upto 30 max

2
Office Attendant Salay in Bihar

  1. Estimated salary range in Bihar
  2. Recommended Latest Office Attendant Recruitment Notifications in Bihar
3
Office Attendant Salay in Rohtas

  1. Estimated salary range in Rohtas
  2. Recommended Latest Office Attendant Recruitment Notificationss for Candidates in Rohtas
4
Office Attendant Salay in Sasaram

  1. Estimated salary range in Sasaram
  2. Recommended Latest Office Attendant Recruitment Notificationss for Candidates in Sasaram
5
How to choose Listings VS Templates?

  1. If category is popular, like Nurse, Bank, Teacher, Clerk, MTS, Assistant then Templates for Bihar, Rohtas, Sasaram
  2. If category is not popular like Investment Manager then Listing
  3. Can we have Blocks for all the states:
  • Bihar
  • Maharashtra
  • UP
  • MP
  • Gujarat

and specific fields for each blocks
bihar_block
maharashtra_block
up_block
mp_block
gujarat_block

Now Consider
Nurse Salary
then
Nurse Salary in Bihar will have custom value of bihar_block

Fetch Latest 5 Nurse listings

Can we have one more block that will fetch latest nurse job listings?

Here Comes Block "Nurse Jobs"..

So list of locks will be following:
  1. Nurse Jobs Block - 1
  2. State-wise blocks - 30
  3. Pillar Blocks - 5 or 10

    (interview, salary, career, recruitment notification with all the external links and pdf links, etc..)

    Blocks or Blogs?
One point to consider:
This approach helps me save a lot of time.. also target top 100 high populated locations. instead of states/districts/cities  and targetting and editing templates everytime,, we can use blocks or targeting top poopulated locations. 

should we??

.. we can target direcrtly the top population locations - kota, sasaram, etc..


X
#

⚠️ Not to do

1
#
2
#
3
#
4
#
5
#
6
#
# Target all posts on linkingsky, indgovtjobs.in, freejobalert.com, etc ...
  • Yes why not...
  1. I can work more than 24 hours a day
  2. No need to target other countries..
  3. No need to create on other niche websites.
  4. Only rely on just one jobsalary.in
  • Try to cover everything in a rush and fail miserably..
  1. Only Create post-wise listings:
    Office Attendant Jobs
    Nurse Jobs
    Chartered Attendant Jobs
  2. Don't target:
    SBI Office Attendant Jobs
    UCO Bank Office Attendant Jobs
    and so on...
  3. Never forget main target pages/queries:
    Latest Nurse Jobs
    Nurse Job Salary in Bihar, MP, etc..
  4. Company-wise Posts should be in nofollow/noindex mode..
    only working for suplimentry content pieces - 
    Organisation
    Post Name
    Salary Range
    Qualification
    Total Vacancy
    Age Limit
    Last Date
    Official Links
  5. Company-wise posts are nofollow/noindex therefore there body will be containing copied content from other websites - not mush effort required..
  6. company-wise postings will take time as well as create duplicary accross website.
  7. Instead of thin content -
    company X post-wise listings.. of same company..
    we can go company-wise listings..

    Example:

    Instead of -
    UCO Bank Branch Manager Salary
    UCO Office Attendant Salary
    UCO Kotlin Developer

    Target -
    UCO Bank Salary (Updated 2026) - 
    Show all posts here.. example - like indgovtjobs.in -
    manual copy pasting.. still too much of time..
    for what?
    to rank UCO Branch Manager Salary?
    Still Useless..
# JAN 29 -  Listing 1 VS Listing 2 VS Template 👀
--
Listing:
Western Coalfields Apprentice Salary - Listing 1

Listing:
Apprentice Jobs - Listing 2

Template:
Apprentice Salary in India, Bihar, Rohtas - Template


Why?
💥 Listing 1:

Evergreen ✅
Western Coalfields Apprentice Salary (2026/2027/...)

Non-duplicate ✅
Salary Comparision with Peers

keeps changing ✅
every time a unique company is compared to the latest 5 companies salaries.

only major change:
unlike job listings this page is about salary so 
instead of job details button it will have check salary button.

Salary comparision table which keeps changing
will have only comparision rows
Pillar posts - Yes...

💥 Listing 2:
Apprentice Jobs
List of all Latest Apprentice Jobs with salary in LPA of the respective companies...
Pillar posts - yes...

💥 Template:
Apprentice Salary in India
estimated salary rangevia listing all companies.

Apprentice Salary in Bihar
state-wise companies only - bihar will have - fishery, electric department, etc.. - ah! will think later..

Apprentice Salary in Rohtas
state-wise companies only - bihar will have - fishery, electric department, etc.. - ah! will think later..

also add pillar posts, latest salary comparision + notifications for updated content.
--
# Create high-trust, location-specific salary pages for 600 locations (30 states X 20 top population cities per state)
--
Alright. I’m going to **lock this idea into a sharp, memorable summary**, and I’ll be **brutally honest** so future-you doesn’t romanticize it or forget the logic.

---

# 🔒 ONE-PAGE IDEA SUMMARY (READ THIS WHEN YOU FORGET)

## 🎯 Core Goal

Create **high-trust, location-specific salary pages** for India that target **long-tail queries** like:

> *Bank Branch Manager Salary in Sasaram*

— without lying, without spam, and without pretending company-level data exists where it doesn’t.

---

## 📉 Scope Control (SMART MOVE)

* ❌ 10,000 locations → **NO**
* ✅ **600 locations MAX**
* ✅ Only **30 states**
* ✅ **Top 20 populated locations per state**
* This keeps crawl quality high and avoids thin-content penalties.

**This alone fixes 60% of SEO risk.**

---

## 🧠 The PROBLEM You Identified (Very Important)

When users search:

> *ICICI Bank Branch Manager Salary in Sasaram*

Google shows:

* Generic bank salary pages
* No exact local answer
* No trustworthy local comparison

Because **exact branch-level salary data does not exist publicly**.

Most sites either:

* Avoid the query
* Or lie (spam)

---

## 🔥 THE TWIST (THIS IS THE WHOLE IDEA)

### ❌ What you will NOT do

* You will NOT claim:

  > “Karnataka Bank Branch Manager salary in Sasaram = ₹X”
* You will NOT say a bank has a branch when it doesn’t.

---

### ✅ What you WILL do (SMART + SAFE)

You will create a **comparison table** like:

> **“Bank Branch Manager Salary Context – Sasaram”**

#### Table logic:

* List **ALL major banks**
* For each bank:

  * Column: **Branch presence in Sasaram** → Yes / No / Nearby District
  * Column: **India-wide average Branch Manager salary**
  * Column: **Adjusted Sasaram salary range (estimate)**

✔ This includes keywords
✔ Avoids false claims
✔ Adds real context
✔ Increases trust

**You are comparing salaries *to* Sasaram, not claiming they exist *in* Sasaram.**

This is the key distinction that keeps you out of spam territory.

---

## 🧩 Page Content Structure (Each Page)

Every location page includes:

1️⃣ **Estimated salary range for the role in that location**

* Based on state + city weight
* Unique for every location

2️⃣ **Bank comparison table**

* Presence: Yes / No / Nearby
* National avg salary
* Adjusted local estimate
* Clear disclaimer: *“Indicative, not branch-specific”*

3️⃣ **State-relevant company mentions**

* “Candidates from Sasaram commonly apply
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
--
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0
#
0

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.