Think about ordering at a café. There is a set of unspoken rules: you queue, the server says 'Next', you say the drink and the size, they repeat it back, you pay, they give you a ticket number. If you sang your order or handed over a drawing, the system would break, even though the café works fine. A network protocol is a written-down set of rules like these: who speaks first, what each message must look like, and what to do when something goes wrong.
Loading one web page uses several protocols stacked in layers. First DNS turns the name schoolnews.org into a numeric address such as 203.0.113.25. Then your browser sends an HTTP request, 'GET /homepage', to that address. Underneath, in most connections, TCP cuts the request into packets, numbers them and re-sends any that are lost. IP puts addresses on each packet so routers can pass it along. Each layer does one job and trusts the layer below to do its own.
A protocol is not a program. HTTP is the rulebook; Chrome, Safari and Firefox are three different programs that all follow it, which is why any of them can open the same site. A protocol is also not the data it carries: a packet is the envelope, while the protocol is the agreement about how envelopes are addressed, numbered and checked.
Think of it like this. A protocol is like the rules of a card game. Two players from different countries can play together if they agree on the rules: what a valid move is, whose turn it is, what happens after a mistake. Change the rules on one side only and the game falls apart. Unlike most games, network protocols are written down exactly, so machines can follow them without arguing.
Core idea. Protocols are layered — higher-level protocols (HTTP) rely on lower-level ones (TCP, IP) to handle the details of delivery.